fix(ci): exclude impit-* from minimumReleaseAge in release workflow#438
Merged
fix(ci): exclude impit-* from minimumReleaseAge in release workflow#438
Conversation
The release workflow publishes platform binaries then immediately runs pnpm install --lockfile-only to refresh the lockfile. With minimumReleaseAge set to 1440, the just-published impit-* packages cannot be locked, so the old version's optionalDependencies entries are removed without the new ones being added — leaving master with a stale lockfile that breaks subsequent --frozen-lockfile installs in PR CI.
github-actions
Bot
added
the
t-tooling
There was a problem hiding this comment.
Pull request overview
This PR updates the impit-node PNPM configuration to prevent freshly published impit-* platform packages from being blocked by minimumReleaseAge during the release workflow’s post-publish lockfile refresh, avoiding stale/broken lockfiles that can later fail --frozen-lockfile installs in CI.
Changes:
- Add
impit-*tominimumReleaseAgeExcludeso newly published platform packages can be resolved immediately duringpnpm install --lockfile-only. - Update
pnpm-lock.yamlto retain theimpit-*optional dependency entries at0.13.1.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| impit-node/pnpm-workspace.yaml | Excludes impit-* from minimumReleaseAge gating so release-time lockfile updates can resolve just-published binaries. |
| impit-node/pnpm-lock.yaml | Regenerates lockfile to include/retain impit-* optionalDependencies and package/snapshot entries. |
Files not reviewed (1)
- impit-node/pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
B4nan
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow publishes platform binaries, then immediately runs
pnpm install --lockfile-onlyto refresh the lockfile.With
minimumReleaseAgeset to1440, the just-publishedimpit-*packages cannot be locked, so the old version'soptionalDependenciesentries are removed without the new ones being added - leavingmasterwith a stale lockfile that breaks subsequent--frozen-lockfileinstalls in PR CI.