Skip to content

chore(release): release 1.0.0-beta.107 - #4912

Open
ScriptedAlchemy wants to merge 2 commits into
masterfrom
release-please--branches--master--components--tracedecay
Open

ScriptedAlchemy wants to merge 2 commits into
masterfrom
release-please--branches--master--components--tracedecay

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

1.0.0-beta.107 (2026-11-17)

Features

  • proximity: retire constant-score threshold controls (27f43b8)

This PR was generated with Release Please. See documentation.

@changeset-bot

changeset-bot Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3fb26d8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ScriptedAlchemy
ScriptedAlchemy marked this pull request as ready for review November 17, 2026 01:42

@devin-ai-integration devin-ai-integration Bot 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.

Devin Review found 1 potential issue.

Devin Review

Comment thread Cargo.toml
[workspace.package]
edition = "2024"
version = "1.0.0-beta.106"
version = "1.0.0-beta.107"

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.

🟡 Release binaries retain the previous version

For beta.107 builds, CARGO_PKG_VERSION remains beta.106 because the generated CLI targets were not refreshed. Both version reporting and upgrade checks use that stale value.

Learn more

Bazel supplies package versions from generated target attributes, independently of the workspace manifest. The CLI build script and binary targets still declare beta.106. The build-version renderer embeds that value, and upgrade checks use it as the installed version. The lockfile also retains beta.106 for version-inheriting workspace packages, which the release integrity guard rejects.

Example: Build the beta.107 release through Bazel. Its CLI version contains 1.0.0-beta.106+<commit> rather than 1.0.0-beta.107+<commit>, and its upgrade check compares beta.106 against the available beta.107 release.

Recommended fix: Refresh and commit the generated release metadata using the operations in the release metadata updater, including Cargo.lock and generated Bazel targets. Run the release integrity guard and verify the Bazel-built CLI reports beta.107.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant