Repository navigation
fix(ci): allow release automation to push changes - #533
Merged
Merged
Conversation
|
| Name | Type |
|---|---|
| @stackoverflow/stacks-editor | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
✅ Deploy Preview for stacks-editor 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
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.
Summary
Fix the release-branch push failure following #519. The release job needs
contents: writeto push the Changesets release branch. The workflow-widedefault remains read-only.
Failed run: https://github.com/StackExchange/Stacks-Editor/actions/runs/36044234546/job/107784922442
Changes
No changeset is needed for this CI-only fix.
How to test
npm ci. Local verification used Node 26.5.0and npm 11.17.0; CI uses Node LTS.
npm run test:release-config: all six tests pass. The updated assertionwas also verified to fail against the original read-only release job.
npm run lintand./node_modules/.bin/tsc --noEmit: both pass.Lint reports two warnings in unchanged stack-snippets tests.
changeset-release/mainand open the separate 1.0.0 release PR.This remote behavior remains unverified; the release job is skipped on PRs.
Full unit, browser, and package-consumer suites were not rerun locally for
this permissions-only change; the existing CI gates remain in place.
No UI changes or manual preview activation are needed.