chore(release): bump to 2026.06.3 - #3037
Merged
Merged
Conversation
- CalVer (YYYY.0M.MICRO); still June 2026, micro 2 -> 3 - Gives Sentry a real release boundary: every build since 2026.6.2 reported the same base version (only the +git-hash differed), so resolved-in-next-release never stuck and fixed issues kept reopening on the next event. A version bump lets the deployed fixes actually clear from the board. - Ships the crash/noise fixes merged since 2026.6.2: SQLite WAL + busy timeout (#3015), celery migration-gate (#3016) and asset-probe soft limits (#3017), transient-redis/CancelledError Sentry filtering + redis healthcheck (#3018/#3028), GitHub update-check log level (#3019), webview respawn on D-Bus death at setup and mid-play (#3020/#3031), resilient static-file scan (#3026), Wayland-socket wait (#3030), and Sentry release/board triage tags (#3021/#3025) Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
|
There was a problem hiding this comment.
Pull request overview
Mechanical CalVer bump to 2026.06.3 to ensure Sentry’s resolvedInNextRelease has a new base release boundary (avoiding the prior situation where builds only differed by +<git-hash> metadata).
Changes:
- Bump Python project version in
pyproject.tomlto2026.06.3. - Bump JS package version in
package.jsonto2026.06.3. - Update the locked editable package version in
uv.lock(normalized to2026.6.3per Python version normalization).
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pyproject.toml |
Updates Anthias Python package CalVer to 2026.06.3. |
package.json |
Updates frontend/package CalVer to 2026.06.3. |
uv.lock |
Updates locked editable anthias package version to 2026.6.3 (normalized form). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Issues Fixed
Unblocks the Sentry board. Every build since 2026.6.2 has reported the same base release version
2026.6.2(only the+<git-hash>build-metadata differed), soresolvedInNextReleasecould never take effect — Sentry kept reopening fixed issues on the next event. Concrete evidence from this morning's sweep, ANTHIAS-9's release spread:All the same base version → no "next release" boundary. Bumping to 2026.06.3 creates one, so the fixes already deployed actually clear and future resolves stick.
Description
Mechanical CalVer bump (mirrors #3009):
pyproject.toml,package.json,uv.lock. No code change.This ships the crash/noise fixes merged since 2026.6.2 — SQLite WAL + busy timeout (#3015), celery migration-gate (#3016) and asset-probe soft limits (#3017), transient-redis/
CancelledErrorSentry filtering + redis healthcheck (#3018/#3028), GitHub update-check log level (#3019), webview respawn on D-Bus death at setup/mid-play (#3020/#3031), resilient static-file scan (#3026), Wayland-socket wait (#3030), and the Sentry release/board-triage tags (#3021/#3025).Note: merging this is just the version bump. Publishing the GitHub release + OTA deploy to the fleets remains a separate, deliberate step (per the usual release sequencing). Recommend merging #3032 (display_power
DataError) and #3036 (celery redis-backend log noise) first so they ride the same release.Checklist
🤖 Generated with Claude Code