Skip to content

Bump version to 26.11.0 - #333

Open
salmanfarisvp wants to merge 1 commit into
masterfrom
release-26.11.0
Open

salmanfarisvp wants to merge 1 commit into
masterfrom
release-26.11.0

Conversation

@salmanfarisvp

Copy link
Copy Markdown
Member

Bumps the version to 26.11.0 in Cargo.toml, Cargo.lock, Dockerfile and action.yml.

Covers the 19 commits merged since v26.9.0. After merge, tag v26.11.0 on master to trigger the release workflow, then bump the Homebrew tap.

Copilot AI lite review requested due to automatic review settings November 12, 2026 08:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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 renatgalimov left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:latest container (rustc 1.99.1), cargo build --locked and cargo test --locked on master @ 2315b5f (the PR's base), then on the PR head @ d4ff2ac.
  • screenly --version: master prints screenly 26.9.0. PR prints screenly 26.11.0.
  • --locked build: passes on both. So Cargo.lock matches Cargo.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.0 is left anywhere in the tree.
  • Version choice: the README's CalVer rule (YY.M.MICRO, MICRO starts at 0 each month). The latest tag is v26.9.0. There is no v26.10.* or v26.11.* tag or release, so 26.11.0 is 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.yml and sbom.yml run on v* tag pushes and take the version from the tag. The MCP bundle's 0.0.0 placeholder is replaced with the tag, and the release Docker job passes --build-arg RELEASE=<tag>. flake.nix reads the version from Cargo.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

PR #333 diagram

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants