chore(deps): let first-party magic packages update immediately - #26
Merged
Conversation
GSTJ
force-pushed
the
fix/pnpm-first-party-release-age
branch
from
August 5, 2026 01:37
9d01a9d to
bc5f50a
Compare
GSTJ
changed the title
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
1 participant
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.
Summary
The pnpm release-age policy now lets GSTJ's
magic-*packages update immediately, matching the shared Renovate preset.Details
magic-*exclusions with the package-name pattern used by magic v1.12.5.Testing steps
corepack pnpm install --frozen-lockfile --ignore-scripts corepack pnpm audit corepack pnpm run build corepack pnpm run lint corepack pnpm run format corepack pnpm run typecheck corepack pnpm test corepack pnpm run changelog:check npm pack --dry-run