Skip to content

chore(release): release 1.0.0-beta.106 - #4908

Merged
ScriptedAlchemy merged 2 commits into
masterfrom
release-please--branches--master--components--tracedecay
Nov 16, 2026
Merged

ScriptedAlchemy merged 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.106 (2026-11-16)

Features

  • explorer: stream request-owned results for exact projects (5eb0f2c)
  • explorer: stream results for exact projects (80ebe1b)

Bug Fixes

  • explorer: box streamed source event payload (7227aeb)
  • explorer: close stream review findings (5207c2b)
  • explorer: distinguish cancellation from cleanup failure (9b183c1)
  • explorer: report stream cleanup failures (e1a835c)

This PR was generated with Release Please. See documentation.

@changeset-bot

changeset-bot Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 649c2c5

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 16, 2026 16:41

@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.105"
version = "1.0.0-beta.106"

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 binary retains previous version

After workspace.package.version advances, Cargo.lock and generated Bazel targets still say beta.105. The release integrity guard rejects this head; an unguarded Bazel build reports beta.105 for beta.106.

Learn more

The version bump changes the workspace package version, which every workspace crate inherits. The current lockfile and generated Bazel rules still embed beta.105. The release integrity guard compares local package versions against Cargo.lock and rejects this PR head. Bazel sets the binary's package version from its generated target, so building this head without the guard reports the old version. The release PR workflow normally adds a generated-metadata commit before marking the PR ready.

Example: A beta.106 checkout still has version = "1.0.0-beta.105" on the CLI Bazel target. The integrity guard fails, while a manually built CLI reports beta.105 instead of beta.106.

Recommended fix: Let scripts/update-release-pr-lockfile.sh complete and include its Cargo.lock and generated BUILD.bazel changes in the release PR before merge; confirm the integrity guard passes.

Devin Review


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

@ScriptedAlchemy
ScriptedAlchemy merged commit 3aa9cb3 into master Nov 16, 2026
14 checks passed
@ScriptedAlchemy

Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

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