Skip to content

chore(deps): cover fixture workspace and add 7-day cooldown in dependabot - #306

Open
simongdavies wants to merge 1 commit into
mainfrom
simongdavies-dependabot-fixture-lock-and-cooldown
Open

simongdavies wants to merge 1 commit into
mainfrom
simongdavies-dependabot-fixture-lock-and-cooldown

Conversation

@simongdavies

Copy link
Copy Markdown
Member

What

  • Add src/hyperlight-js-runtime/tests/fixtures/extended_runtime to the cargo update config.
  • Set a 7-day cooldown (cooldown.default-days: 7) on all three update configs.

Why

extended_runtime is a standalone cargo workspace with its own Cargo.lock, and CI validates it with just check-fixture-lock (cargo metadata --locked). Dependabot only tracked /, so when it bumped a hyperlight-js-runtime dependency the fixture lock went stale and CI failed — see #276, where base64 0.22 → 0.23 in src/hyperlight-js-runtime/Cargo.toml left the fixture lock pinned at 0.22.1:

error: the lock file .../extended_runtime/Cargo.lock needs to be updated but --locked was passed to prevent this
error: recipe `check-fixture-lock` failed on line 246 with exit code 101

The cooldown (up from the 3-day default) reduces daily PR churn and lets releases settle before we pick them up.

Caveat

Dependabot raises a separate PR per directory, so a root bump and the matching fixture-lock bump won't land in the same PR. This keeps the fixture lock from going permanently stale, but a version bump may still need a manual cargo update --manifest-path src/hyperlight-js-runtime/tests/fixtures/extended_runtime/Cargo.toml -p <crate> on the root PR to get it green. If that turns out to be frequent, a groups entry spanning both directories would combine them.

src/hyperlight-js-runtime/tests/fixtures/native_math also has its own lock, but nothing in the root workspace can invalidate it, so it's left out here.

…abot

Add src/hyperlight-js-runtime/tests/fixtures/extended_runtime to the cargo update config. It is a standalone workspace with its own Cargo.lock that CI validates via `just check-fixture-lock`, so it drifts out of sync when Dependabot bumps a hyperlight-js-runtime dependency in the root workspace.

Also set a 7-day cooldown on all three update configs to reduce PR churn.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
@simongdavies simongdavies added kind/dependencies Dependency updates ready-for-review PR is ready for (re-)review labels Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/dependencies Dependency updates ready-for-review PR is ready for (re-)review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant