Repository navigation
chore(deps): take the three exactly-pinned packages to their current release - #6
Merged
Merged
Conversation
…release @astrojs/sitemap 3.7.3 to 3.7.4, and both @fontsource-variable faces 5.2.6 to 5.3.0. All three are pinned to an exact version rather than by range, so `npm update` cannot reach them — which is why they had gone stale while astro, carried by `^7.1.4`, had not: main already resolves it to 7.3.2. package.json moves by those three version literals and nothing else. No package is promoted out of the transitive tree into a direct dependency, which is what `npm install <pkg>@latest` does and why it was not used. The lock also drops stream-replace-string, which sitemap 3.7.4 no longer requires. typescript stays at 5.7.3. 7.0.2 is a major, and @astrojs/check declares a typescript peer of `^5.0.0 || ^6.0.0`, so taking it would break the type-check that the ci workflow gates on. Verified: `astro check` reports 0 errors, 0 warnings and 0 hints across 69 files, `npm audit` reports zero vulnerabilities, and the site builds all 33 pages — the same count as before the bump. Spec: GOV-R12 Signed-off-by: Wessel Verheij <info@nightworks.io>
github-actions
Bot
added
the
dependencies
📎 Spec referencesThis PR cites the following spec identifiers:
Updated automatically on each push. |
|
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.
What
Three packages in
package.jsonare pinned to an exact version rather than by range, sonpm updatecannot reach them. They had gone stale whileastro— carried by^7.1.4— had not:mainalready resolves it to 7.3.2.@astrojs/sitemap@fontsource-variable/inter@fontsource-variable/jetbrains-mononpm updatewas run first and reported the tree already up to date — nothing inside a declared range had moved.package.jsonthen changes by those three version literals and nothing else; no package is promoted out of the transitive tree into a direct dependency, which is whatnpm install <pkg>@latestdoes and why it was not used. The lock additionally dropsstream-replace-string, which sitemap 3.7.4 no longer requires.Not taken
typescript5.7.3 → 7.0.2 is a major, and@astrojs/checkdeclares atypescriptpeer of^5.0.0 || ^6.0.0. Taking it would put the tree outside that peer range and breaknpm run check, which theciworkflow gates on. It unblocks when@astrojs/checkwidens.Verification
npm run check— 0 errors, 0 warnings, 0 hints across 69 filesnpm run build— 33 pages, unchanged from before the bumpnpm audit— zero vulnerabilities, before and afterThis is staleness rather than a vulnerability response:
npm auditreported zero advisories on both sides of the change.Spec: GOV-R12