chore: remove update-readme-on-release workflow#34
Merged
Conversation
The workflow attempted to auto-create a PR after each release to bump README version metadata, but: - README is already updated as part of the release PR (version, date, features, roadmap, CHANGELOG) — workflow only duplicated 2 lines. - Default GITHUB_TOKEN cannot create PRs; enabling that org-wide permission widens the supply-chain attack surface for cosmetic gain. - Latest run failed for v2.4.0 with: 'GitHub Actions is not permitted to create or approve pull requests.' Release process going forward stays manual inside the release PR.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
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.
Why
The
update-readme-on-release.ymlworkflow attempted to auto-create a PR after each release to bump README version metadata. It failed on v2.4.0 with:Decision: remove rather than fix
**Current Version**and**Released**).Process going forward
The release SOP stays inside the release PR (manual, reviewed):
release/vX.Y.Zfrom masterdoc.go,README.md,docs/V2_*.mdCHANGELOG.md+RELEASE_NOTES_vX.Y.Z.mdgit tag+gh release create