chore(deps): release pending dependency updates#82
Merged
Conversation
PR #81 (chore: update deps, adapt to react-router 7.16) merged without a `deps` scope, so semantic-release cut no release — the react-router 7.16 dependency bumps shipped to main unreleased, and the lockfile's esbuild@~0.25.12 entry was left uncommitted. Commit the missing deno.lock entry and land it under the `deps` scope so a patch release publishes the pending dependency updates (matching the #77 catch-up). Document the deps-scope requirement in CONTRIBUTING.md so future dependency PRs publish reliably. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 0.4.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
PR #81 (
chore: update deps, adapt to react-router 7.16) merged without thedepsscope, so semantic-release matched no release rule and cut no version.The react-router 7.16 dependency bumps have been sitting on
mainunreleased,and the lockfile's
esbuild@~0.25.12entry was never committed. This is thesame gap #77 (
chore(deps): release prior dependency updates) had to patch up.This PR lands the missing lock entry under the
depsscope so a patch releasepublishes the pending dependency updates, and documents the scope requirement so
it stops recurring.
Changes
npm:esbuild@~0.25.12entry from the chore: update deps, adapt to react-router 7.16 #81dependency bump (
deno installconfirms the lock is otherwise consistent).depsscope(
chore(deps):/build(deps):→ Patch); plainchore:/build:publishesnothing. Updated both the commit-types table and the Release Process list.
Why no release happened
.releaserc.jsonreleases dependency commits only with thedepsscope:{ "type": "build", "scope": "deps", "release": "patch" }, { "type": "chore", "scope": "deps", "release": "patch" }Plain
chore: update deps(as in #76, #79, #81) matches nothing → no release.Merging this PR will trigger a patch release (0.4.3) capturing the pending
dependency updates.
Testing
No code change — lockfile + docs only.
deno installreports no further lockdrift;
deno fmt --check CONTRIBUTING.mdpasses. CI runs the full suite.🤖 Generated with Claude Code