chore(dependabot): hold the conventionalcommits preset at 9.x - #623
Merged
Conversation
#616 pinned conventional-changelog-conventionalcommits to ^9.3.1 to unbreak the release pipeline, and Dependabot immediately proposed ^10.4.0 again in the next dev-dependencies group (#620). Merging that would restore the exact failure #616 fixed: the 10.x line requires conventional-changelog-writer@9, semantic-release 25 bundles a generator depending on writer ^8, and generateNotes dies before any release is cut. The hold was missing from the batch added in #617 — an oversight, since #616 had pinned it minutes earlier.
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.
Description
#616 pinned
conventional-changelog-conventionalcommitsto^9.3.1to unbreak the release pipeline. Dependabot immediately proposed^10.4.0again in the next dev-dependencies group (#620).Merging that would restore the exact failure #616 fixed: the 10.x line requires
conventional-changelog-writer@9,semantic-release@25bundles@semantic-release/release-notes-generator@14which depends on writer^8, andgenerateNotesdies withbefore any release is cut — blocking all app releases, as it did earlier tonight.
The hold was missing from the batch added in #617; that was an oversight, since #616 had pinned the package minutes before.
Type of Change
How Has This Been Tested?
YAML parses; the ignore list now covers nine packages. #617's holds are already confirmed working — the regenerated group PR (#620) no longer carries TypeScript 7, where its predecessor (#606) did.
Checklist
Additional Notes
Only majors are held; 9.x minors and patches still flow. Unhold this alongside a semantic-release major that ships a writer-9 generator.
#620 should not be merged until this lands, and even then it wants a look: it also carries
vitestand@vitest/coverage-v84 → 5,@semantic-release/changelog6 → 7,@semantic-release/git10 → 11, and@changesets/changelog-github0.7 → 1.0. Those are majors riding inside a grouped dev-dependency bump, and the changesets one interacts with the CLI v2-vs-v3 question left open by the 1.0 graduation merge reverting #593.