ci: wire up changesets release/publish workflows for go-web#32
Merged
Conversation
✅ Deploy Preview for lynx-go-web ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
This PR adapts the Changesets release/publish workflows copied from a monorepo to fit this repository (single package +
example/example-rspress). It also clarifies CI vs release vs publish execution so regular PRs and regularmainpushes won’t accidentally trigger publishing.What changed
workflow-test.yml: reworked into a repo-specific dedicated test workflow (pnpm typecheck+ buildexample+ buildexample-rspress) to be reused by other workflows.ci.yml: runs only on PRs and reusesworkflow-test.yml(no extra write permissions needed).release-pr.yml: onmainpushes, runschangesets/actionto create/update the release PR.publish.yml:detect-version-packagesgating so publishing only happens when merging achangeset-release/*PRid-token: write+NPM_CONFIG_PROVENANCEto prepare for OIDC/Trusted Publishing (noNODE_AUTH_TOKENrequired).ci-setupcomposite action: addsregistry-urland apackage-manager-cachetoggle so publish can opt into a clean, no-cache install while CI stays cached by default.Verification
pnpm typecheck