chore(release): bump to 1.5.6#544
Merged
Merged
Conversation
Cuts the patch release containing the four bug fixes merged today (#540 cost hint, #541 mcp-install path, #542 dry-run vision guard, #543 report synthesize hint) plus the attachments docs (#535). Pre-bumps __version__.py and re-renders the version artifacts (render_site.py, render_site_markdown.py, render_server_card.py) so auto-tag.yml hits its "nothing to commit" path and only tags v1.5.6 — its direct version-bump push to main is currently rejected by branch protection (GH013), which is why applying semver:patch to a regular fix PR (#543) failed to release. Filing that pipeline issue separately. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying synthpanel with
|
| Latest commit: |
eccee90
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://40c9e735.synthpanel.pages.dev |
| Branch Preview URL: | https://release-v1-5-6.synthpanel.pages.dev |
claude-dataviking
requested review from
openclaw-dv and
the-data-viking
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cuts v1.5.6 — the four bug fixes merged today (#540, #541, #542, #543) + the attachments docs (#535).
Why this is a pre-bump release PR (not just a labeled fix PR)
Labeling a regular fix PR
semver:patch(#543) madeauto-tag.ymltry to commit the version bump andgit push origin HEAD:main, which branch protection rejected:GH013: Repository rule violations. So no tag/release/publish happened. The github-actions bot lacks a push-bypass onmain.This PR pre-bumps the version artifacts the way auto-tag would (
__version__.py+site/index.html+site/index.md+site/.well-known/mcp/server-card.json, via the three render scripts), so on merge auto-tag hits its "nothing to commit" path, skips the blocked push, and just tagsv1.5.6→publish.yml→ PyPI. Localtest_version_artifacts_in_sync/test_site_markdown/test_well_known_server_cardpass, so CI green here ⇒ auto-tag's render is a no-op diff.Follow-up (separate issue worth filing)
The real fix is to let auto-tag push the bump to
main— either add the github-actions identity to the ruleset's bypass actors (Terraform indataviking-infra), or change RELEASING.md to make pre-bump release PRs the documented flow. Right now the "label any PRsemver:patch" flow in RELEASING.md is broken.🤖 Generated with Claude Code