Repository navigation
chore(release): bump version metadata to 2026.10.0 - #3373
Merged
Merged
Conversation
Same three files as #3348: pyproject.toml and package.json carry the version, uv.lock records it for the editable root package and is regenerated with `uv lock`. 2026.09.0 shipped on 22 September. CalVer puts the next release in October, so the month rolls and MICRO resets to 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
All required version files consistently use the valid October 2026 release number.
Review effort: Balanced
Findings: None
What changed in this PR
Updates Anthias release metadata for the October 2026 CalVer release.
Changes:
- Bumps the release version to
2026.10.0. - Keeps Python, frontend, and lockfile metadata synchronized.
| File | Description |
|---|---|
package.json |
Updates frontend package metadata. |
pyproject.toml |
Updates the canonical project version. |
uv.lock |
Updates the editable Anthias package version. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
vpetersson
approved these changes
Oct 16, 2026
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.
What this does
Bumps the version metadata from
2026.09.0to2026.10.0— the same three files as #3348:pyproject.toml,package.json, anduv.lockregenerated withuv lock.Why
2026.09.0shipped on 22 September. CalVer rolls the month and resets MICRO, so the next release is2026.10.0.There are four commits on
mastersince the tag, and none of them changes an interface:fix(celery): blanket exception handlers were swallowing the soft time limit, so a task that overran was never actually cut off.fix(upgrade): the viewer and celery are now stopped before the image pull, so low-RAM boards do not get OOM-killed mid-upgrade. Worth a look since it changesbin/upgrade_containers.sh, which runs on devices in the field.fix(viewer): cage's Wayland socket is probed by connecting rather than by existence, and the crash tail is drained.chore(deps): GitHub Actions group bump, CI only.How I know this is right
uv lockwrote the lockfile, so the editable root package's version cannot drift frompyproject.toml. The diff is one line in each of the three files and matches #3348 exactly in shape.tests/test_backup_helper.pyhardcodes2026.9.0in a backup manifest fixture — that is a fixed test input for the restore version guard, not a reference to the current version, so it is deliberately left alone.🤖 Generated with Claude Code