Skip to content

release: v4.0.0 - #14

Merged
KeithRaghubar merged 6 commits into
mainfrom
release/v4.0.0
Oct 28, 2026
Merged

KeithRaghubar merged 6 commits into
mainfrom
release/v4.0.0

Conversation

@KeithRaghubar

Copy link
Copy Markdown
Owner

Release v4.0.0. Notes: docs/release-notes/v4.0.0.md

KeithRaghubar and others added 6 commits October 28, 2026 10:21
The main ruleset requires a pull request, so the release script's
`git push origin main` was rejected. release.sh now switches to
release/vX.Y.Z in Phase 1, prompts to push that branch plus the tag,
and requires the branch on --resume. Stage 7 of the checklist opens the
release PR and merges it with a merge commit: a squash would rewrite the
signed release commit and leave the tag outside main's history.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…4.0.0-DEV2)

GitHub caps a release body at 125000 characters and v4.0.0.md is
163585 bytes, so gh release create failed. A notes file over the limit
is now published as its summary plus a link to the full file at the tag.

The failure also left PKGBUILD's sha256sums rewritten, and the resume
then refused the dirty tree. A resume now accepts a PKGBUILD whose only
change is that array (compared with the array removed on both sides).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A PR description is capped at 65536 characters; v4.0.0.md is 163585 bytes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KeithRaghubar
KeithRaghubar merged commit 481e5b5 into main Oct 28, 2026
3 checks passed
@KeithRaghubar
KeithRaghubar deleted the release/v4.0.0 branch October 28, 2026 14:47
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.

1 participant