Skip to content

chore: bump to 1.6.1-dev after cutting 1.6.0 - #137

Merged
rappdw merged 1 commit into
mainfrom
chore/bump-1.6.1-dev
Aug 12, 2026
Merged

chore: bump to 1.6.1-dev after cutting 1.6.0#137
rappdw merged 1 commit into
mainfrom
chore/bump-1.6.1-dev

Conversation

@rappdw

@rappdw rappdw commented Aug 12, 2026

Copy link
Copy Markdown
Owner

Routine post-release housekeeping, per the CLAUDE.md versioning convention.

SANDY_VERSION 1.6.0 → 1.6.1-dev. Two reasons this matters beyond bookkeeping:

  1. The next release number stays reserved until it's actually cut.
  2. _sandy_proxy_ref switches back to its *-dev case, so the proxy builds from the current branch rather than pinning the v1.6.0 tag — which is what makes ./sandy work on a feature branch before it merges.

v1.6.0 is tagged, published, and showing as Latest.

🤖 Generated with Claude Code

Per the CLAUDE.md versioning convention: immediately after cutting a final
release, bump to X.Y.(Z+1)-dev so the next release number stays reserved and
_sandy_proxy_ref returns to its *-dev case (build the proxy from the current
branch) instead of pinning the v1.6.0 tag.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@rappdw
rappdw force-pushed the chore/bump-1.6.1-dev branch from 5ce244c to e136507 Compare August 12, 2026 13:21
@rappdw
rappdw merged commit ea80645 into main Aug 12, 2026
2 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.

1 participant