Repository navigation
Bump version to 26.11.0 - #333
salmanfarisvp wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are present, and the supplied evidence shows the release version is consistently updated across package metadata and distribution integrations.
No open issues 🎉
What changed in this PR
Updates the CLI release version to 26.11.0 across package metadata and distribution integrations, preparing the repository for the corresponding tagged release.
Changes:
- Bumps the Rust package and lockfile versions to
26.11.0. - Updates the Docker image’s default release artifact to
v26.11.0. - Updates the GitHub Action’s default CLI version to
v26.11.0.
| File | Description |
|---|---|
| Dockerfile | Updates the default downloaded release artifact to v26.11.0. |
| Cargo.toml | Sets the package version to 26.11.0. |
| Cargo.lock | Synchronizes the locked package version to 26.11.0. |
| action.yml | Updates the default GitHub Action CLI version to v26.11.0. |
Review effort: Lite
renatgalimov
left a comment
There was a problem hiding this comment.
What this change does: Moves the CLI version from 26.9.0 to 26.11.0 in Cargo.toml, the crate's own Cargo.lock entry, the Dockerfile default RELEASE and the GitHub Action's default cli_version. Nothing else changes. Pushing the tag v26.11.0 after merge starts the release build.
What I tested
- Setup:
rust:latestcontainer (rustc 1.99.1),cargo build --lockedandcargo test --lockedon master @ 2315b5f (the PR's base), then on the PR head @ d4ff2ac. screenly --version: master printsscreenly 26.9.0. PR printsscreenly 26.11.0.--lockedbuild: passes on both. SoCargo.lockmatchesCargo.toml, and the build left both trees clean.cargo test: 222 passed, 0 failed on both.- Diff: 4 files, +4/-4. No other crate's lock entry changes. No
26.9.0is left anywhere in the tree. - Version choice: the README's CalVer rule (
YY.M.MICRO, MICRO starts at 0 each month). The latest tag isv26.9.0. There is nov26.10.*orv26.11.*tag or release, so26.11.0is the right next value this month. The change touches the same four files as #318 (26.9.0) and #313 (26.8.0). - Release path:
release.ymlandsbom.ymlrun onv*tag pushes and take the version from the tag. The MCP bundle's0.0.0placeholder is replaced with the tag, and the release Docker job passes--build-arg RELEASE=<tag>.flake.nixreads the version fromCargo.toml. No other file holds the version.
No findings.
Note (not new, #318 did the same): as soon as this merges, screenly/cli@master without cli_version tries to download v26.11.0. That download returns 404 until the tag's release build finishes. Push the tag right after merging.
Verdict: Ship.
Diagram of this PR's diff
Bumps the version to
26.11.0inCargo.toml,Cargo.lock,Dockerfileandaction.yml.Covers the 19 commits merged since v26.9.0. After merge, tag
v26.11.0on master to trigger the release workflow, then bump the Homebrew tap.