Version Packages - #1
Merged
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Release PR generated by changesets, opened manually because the workflow could not.
What this does
Bumps both packages to
0.1.1and adds the per-package READMEs to npm.@kud/segment@kud/segment-cli@kud/segment-cli's pin on@kud/segmentwas updated automatically.Why it was opened by hand
The
Releaseworkflow pushedchangeset-release/mainsuccessfully, then failed at PR creation:That is a repository setting, not a workflow bug — Settings → Actions → General → Workflow permissions → "Allow GitHub Actions to create and approve pull requests". Until it is enabled, every release needs this manual step.
Merging this
Merging publishes both packages to npm over OIDC. This is the first release to go through trusted publishing rather than a manual
npm publish, so it doubles as the check that the trusted publisher is wired correctly.