Skip to content

ci: let the lockfile refresh pass Nub's age gate - #2059

Merged
yamcodes merged 1 commit into
v1from
cursor/lockfile-age-gate-036b
Oct 9, 2026
Merged

yamcodes merged 1 commit into
v1from
cursor/lockfile-age-gate-036b

Conversation

@yamcodes

@yamcodes yamcodes commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Autofix rewrites nub.lock with nub install --lockfile-only, then the other jobs can install. That rewrite aborts when the resolve wants a version younger than 24 hours (ERR_NUB_NO_MATURE_MATCHING_VERSION). On #2040 that version is [email protected]. Autofix never commits the lockfile, so pkg-pr-new, check-sync, and the test jobs stay on ERR_NUB_OUTDATED_LOCKFILE.

This passes --minimum-release-age=0 on that refresh only, which is the off switch Nub documents for the age gate. The following nub install in the same job, and every other workflow, still use the normal gate.

TODO(2057) covers removing the step, including this flag, once renovatebot/renovate#44422 is on the hosted Mend app.

After this merges, re-run autofix on #2040. The follow-up run is the one that can install.

Open in Web Open in Cursor 

nub install --lockfile-only aborts when the resolve wants a version
younger than 24 hours, so autofix never commits nub.lock and the other
jobs stay on ERR_NUB_OUTDATED_LOCKFILE. Turn the gate off for that
refresh only.

Co-authored-by: Yam Borodetsky <[email protected]>
@changeset-bot

changeset-bot Bot commented Oct 9, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: f22a247

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

A one-line CI fix in .github/workflows/autofix.yml that lets the autofix lockfile refresh pass Nub's release-age gate.

  • Refresh lockfile passes --minimum-release-age=0 — the resolve no longer aborts with ERR_NUB_NO_MATURE_MATCHING_VERSION when Renovate has bumped a package to a version still inside the default 24-hour cooling window, so autofix.ci can commit a fresh nub.lock and downstream jobs stop failing on ERR_NUB_OUTDATED_LOCKFILE. The gate stays in force for the following nub install and every other workflow.
  • Expanded TODO(2057) comment — records why the flag is needed and that it goes away once renovatebot/renovate#44422 is on the hosted Mend app.

Verified against the pinned toolchain: Nub is pinned to 0.9.3, and the v0.9.3 release binary advertises --minimum-release-age=<duration> with 0 as the documented per-run off switch (and carries ERR_NUB_NO_MATURE_MATCHING_VERSION); --lockfile-only is a documented nub install flag. The change matches Nub's documented behavior exactly, and scoping the gate-off to this single prefixed command keeps the rest of the pipeline on the normal gate.

Pullfrog  | View workflow run | Using deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏

@github-actions github-actions Bot added the github actions Pull requests that update GitHub Actions code label Oct 9, 2026
@yamcodes
yamcodes merged commit 4e0e821 into v1 Oct 9, 2026
17 checks passed
@yamcodes
yamcodes deleted the cursor/lockfile-age-gate-036b branch October 9, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants