Skip to content

Release: build on a release published in the UI; drop the changelog version check - #65

Merged
HarryCordewener merged 2 commits into
mainfrom
claude/project-thread-8ne9gn
Oct 25, 2026
Merged

HarryCordewener merged 2 commits into
mainfrom
claude/project-thread-8ne9gn

Conversation

@HarryCordewener

@HarryCordewener HarryCordewener commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

Releases are cut on the Releases page now that immutable releases are off.

  • release.yml runs on release: published instead of a tag push. It builds the tag and attaches the four packages to that release with gh release upload --clobber, so a re-run replaces them. If the release was published with empty notes, they are filled from the changelog: the version's section, else [Unreleased]. Notes written in the UI are kept. The draft step and the "already published" guard are gone.
  • The changelog version check (release-check) is removed. Only the tag's shape (v<semver>) is checked, because the installer's file version is derived from it.
  • CHANGELOG.md: [0.1.2] becomes [0.1.4]. v0.1.2 and v0.1.3 were published while immutability was on and can't take files. The README status line follows.
  • docs/RELEASING.md describes the UI flow.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YByKyNUrQMBphzHhXneQEY

A tag no longer needs a dated changelog section to build. The notes are the
tag's section, else [Unreleased], else notes GitHub generates. The 0.1.2
section becomes 0.1.4: v0.1.2 and v0.1.3 have published releases and are
immutable.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YByKyNUrQMBphzHhXneQEY
@coderabbitai

coderabbitai Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Caution

Review failed

The pull request is closed.

Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Publishing a release on the Releases page now runs the workflow, which
builds the tag and attaches the four packages to that release. Notes left
empty are filled from the changelog. The tag-push trigger and the draft
step are gone; immutability is off on the repository.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YByKyNUrQMBphzHhXneQEY
@HarryCordewener HarryCordewener changed the title Release: drop the changelog version check Release: build on a release published in the UI; drop the changelog version check Oct 25, 2026
@HarryCordewener
HarryCordewener marked this pull request as ready for review October 25, 2026 23:40
@HarryCordewener
HarryCordewener merged commit 1686ce6 into main Oct 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants