chore: stop renovate churn on self-published impit-* packages - #531
Merged
Conversation
B4nan
added
t-tooling
B4nan
changed the title
This was referenced Aug 27, 2026
barjin
approved these changes
Aug 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
3 participants
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
impit-*platform packages inimpit-node'soptionalDependenciesare our own napi-rs binary packages, published by the release workflow and version-synced bypnpm copy-versionat release time. Renovate treats them as third-party deps and opens one PR per package after every release (see #525 to #528), and merging those one by one causes conflicts.Renovate changes:
impit-*packages are ignored entirely; the release workflow owns those versions.!/^0/rule. 0.x minors stay separate, since those can be breaking under semver-0 conventions. The group is renamed to "non-major dependencies" so the name covers everything in it.This PR also finishes the parts of the 0.14.4 release that the release run left behind (its commit-back to master was rejected by branch rules): the loader
versionandoptionalDependenciesare bumped to 0.14.4 to match npm, and the missing 0.14.4 changelog entry is added, generated with git-cliff using the same arguments as the workflow. Thejs-0.14.4tag and the GitHub release were created separately, since those don't live in the repo.