GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — ci: remove changelog rollover from release workflow by mikolalysenko · Pull Request #97 · SocketDev/socket-patch

Conversation

@mikolalysenko

@mikolalysenko Mikola Lysenko (mikolalysenko) commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Removes the changelog-rollover job from the release workflow. After publishing, that job committed a chore(changelog): roll [Unreleased] over to vX.Y.Z change directly back to main. Branch protection rejects that push every time:

remote: error: GH013: Repository rule violations found for refs/heads/main.
remote: - Required workflow 'Audit GHA Workflows' is not satisfied
remote: - Changes must be made through a pull request.
remote: - Commits must have verified signatures.
! [remote rejected] HEAD -> main (push declined due to repository rule violations)

So the job failed every release while adding no value.

Changes

  • Delete the changelog-rollover job and scripts/rollover-changelog.sh.
  • Simplify the version job's CHANGELOG check to require an explicit ## [X.Y.Z] heading. It previously also accepted a non-empty ## [Unreleased] section as a stand-in for the post-publish stamp the rollover job would write — that path no longer exists.

New flow

Maintainers rename ## [Unreleased] → ## [X.Y.Z] — DATE by hand in the version-bump PR (the same PR that bumps Cargo.toml). No post-release push to main, so nothing fights branch protection.

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@mikolalysenko @claude
ci: remove changelog rollover from release workflow
48f05a4
The changelog-rollover job committed a "roll [Unreleased] over to vX.Y.Z"
change directly back to main after publishing. Branch protection rejects
that push (required workflow not satisfied, changes must go through a PR,
commits must be signed), so the job failed every release without adding
value.

Remove the job and its scripts/rollover-changelog.sh helper. Maintainers
now rename `## [Unreleased]` to `## [X.Y.Z] — DATE` by hand in the
version-bump PR. The version job's CHANGELOG check is simplified to
require an explicit `## [X.Y.Z]` heading (it no longer accepts a
non-empty [Unreleased] section as a stand-in for the post-publish stamp).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@mikolalysenko

Mikola Lysenko (mikolalysenko) commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator Author

This turned out to be a dumb idea

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mikolalysenko
Mikola Lysenko (mikolalysenko) enabled auto-merge (squash) June 2, 2026 18:56
Wenxin-Jiang
Wenxin Jiang (Wenxin-Jiang) approved these changes Jun 2, 2026
View reviewed changes
@mikolalysenko
Mikola Lysenko (mikolalysenko) merged commit 5b4e513 into main Jun 2, 2026
43 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@mikolalysenko
Mikola Lysenko (mikolalysenko) deleted the chore/remove-changelog-rollover branch June 2, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Wenxin-Jiang Wenxin Jiang (Wenxin-Jiang) Wenxin-Jiang approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@mikolalysenko @Wenxin-Jiang
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.