Skip to content

fix: auto-merge back-merge PR and sync VERSION after release#73

Merged
patrickschaper merged 2 commits into
developmentfrom
fix/release-back-merge-auto-merge
May 21, 2026
Merged

fix: auto-merge back-merge PR and sync VERSION after release#73
patrickschaper merged 2 commits into
developmentfrom
fix/release-back-merge-auto-merge

Conversation

@patrickschaper

Copy link
Copy Markdown
Owner
  • Enable --auto --merge on the maindevelopment back-merge PR created by the release workflow, so VERSION stays in sync without manual intervention
  • Bump VERSION to 0.1.1 to match the latest release tag (was stuck at 0.0.10)

patrickschaper and others added 2 commits May 21, 2026 15:19
- insert RGB(0,32,0) and RGB(0,63,0) between black and the first xterm dim green (95)
- bridges the xterm-256 cube gap for a more gradual fade trail at the dim end
- palette grows from 11 to 13 levels

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- enable auto-merge on the main→development back-merge PR so VERSION
  stays in sync after each release without manual intervention
- bump VERSION to 0.1.1 to match the latest release tag

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@patrickschaper patrickschaper enabled auto-merge (squash) May 21, 2026 13:25
@patrickschaper patrickschaper merged commit ed4ca60 into development May 21, 2026
4 checks passed
@patrickschaper patrickschaper deleted the fix/release-back-merge-auto-merge branch May 21, 2026 13:25
This was referenced May 21, 2026
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