chore(release): bump version metadata to 2026.07.2 - #3188
Merged
Conversation
The v2026.07.2 tag and GitHub release were published (2026-07-13) but the version-bump commit never landed on master, so the version metadata still reported 2026.07.1. - package.json / pyproject.toml: 2026.07.1 -> 2026.07.2 - uv.lock anthias entry: 2026.7.1 -> 2026.7.2 (no dependency changes, QA'd image set unaffected; `uv lock --check` passes) pyproject's version is what anthias_common.version.get_anthias_release() reads, so this restores the correct release string in System Info, the v2 info API, and the outbound User-Agent. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
|
There was a problem hiding this comment.
Pull request overview
This PR restores the in-repo release metadata to match the already-published v2026.07.2 tag, ensuring the application reports the correct release version in places that read from repo metadata.
Changes:
- Bump Python project version in
pyproject.tomlfrom2026.07.1→2026.07.2. - Bump JS package version in
package.jsonfrom2026.07.1→2026.07.2. - Update the
anthiasentry inuv.lockfrom2026.7.1→2026.7.2(normalized form).
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
pyproject.toml |
Updates Python package/project version metadata to 2026.07.2. |
package.json |
Updates JS package version metadata to 2026.07.2 (see SemVer comment). |
uv.lock |
Updates locked editable package version for anthias to 2026.7.2. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "name": "anthias", | ||
| "version": "2026.07.1", | ||
| "version": "2026.07.2", |
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
None. Housekeeping — the version-bump commit for the already-published
v2026.07.2release never landed onmaster.Description
v2026.07.2was tagged and released on GitHub on 2026-07-13 (on the Pi 2/3 blank-screen fix), but the accompanying version bump was missed, so the in-repo version metadata still reported2026.07.1.package.json/pyproject.toml:2026.07.1→2026.07.2uv.lockanthias entry:2026.7.1→2026.7.2(no dependency changes; QA'd image set unaffected;uv lock --checkpasses)pyproject.toml's version is the sourceanthias_common.version.get_anthias_release()reads, so this restores the correct release string in the System Info page, the v2 info API, and the outbound User-Agent — all of which were self-reporting2026.07.1on devices actually running2026.07.2.Reviewed the docs: install pages link to
releases/latestdynamically and there is no in-repo changelog, so no prose docs needed updating.Checklist
🤖 Generated with Claude Code