Repository navigation
chore(vue-scroller): release to require the fixed @fastkit/scroller - #322
Merged
Merged
Conversation
Releasing @fastkit/scroller@1.0.1 (#318) did not release @fastkit/vue-scroller, since its `^1.0.0` range already admitted the new version. Add a patch changeset so its published range becomes `^1.0.1` and updating @fastkit/vue-scroller brings the fix along. Document when a fix in a dependency needs a changeset for its dependents too. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: c856faf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Merged
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.
Summary
#318 fixed
missing elementin@fastkit/scroller(released as1.0.1in #319), but@fastkit/vue-scrollerwas not released with it: its published range^1.0.0already admits1.0.1, so changesets left it alone. Consumers who update@fastkit/vue-scrollercan keep the unfixed@fastkit/scrollerin their lockfile, even though the bug surfaces throughuseScrollerControl({ el: 'self' }).#318's description said
@fastkit/vue-scrollerwould follow via the internal dependency update. That was wrong;updateInternalDependencies: "patch"only rewrites the range when the dependent is being released anyway.Changes
@fastkit/vue-scrollerpatch. Itsworkspace:^dependency is published as^1.0.1, raising the floor to the fixed version.docs/release.md: new section "Delivering a fix in a dependency to its dependents" explaining when a dependent needs its own changeset.🤖 Generated with Claude Code