setup changesets and release automation + bonus actions#77
Merged
Conversation
🦋 Changeset detectedLatest commit: 261f066 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 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
stipsan
commented
Aug 28, 2025
Member
Author
stipsan
commented
Aug 28, 2025
| "image-url" | ||
| ] | ||
| ], | ||
| "packageManager": "pnpm@10.15.0" |
Member
Author
There was a problem hiding this comment.
The release.yml reusable action requires pnpm to be used, and scripts.release to have changeset publish.
bjoerge
approved these changes
Aug 28, 2025
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
2 participants
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.
I've already configured https://github.com/apps/changeset-bot for this repo, and updated the npm listing https://www.npmjs.com/package/@sanity/image-url?activeTab=versions to enable trusted publishing (OIDC) which is why you don't see a
secrets.NPM_PUBLISH_TOKENused anywhere. Merging this will open a PR that says "Version Packages", merging that one will run the release flow, similar to how repos on release-please operate.