Version Packages - #49
Merged
s0 merged 1 commit intoJan 27, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
s0
previously approved these changes
Jan 27, 2026
Copy link
Copy Markdown
Member
|
We should land this first: #48 and actually, maybe we'll have to tweak some permissions related to id-token too? I need to double check that |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
id-token should already be good, as this repo already was using provenance, so had id-tokens set-up: Line 1 in 3d63783 ghcommit/.github/workflows/release-and-publish.yaml Lines 8 to 11 in 3d63783 |
Sorry, something went wrong.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
b4080fe to
8d5d614
Compare
January 27, 2026 17:59
s0
approved these changes
Jan 27, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@changesets/ghcommit@2.0.1
Patch Changes