Skip to content

Rust #325: compare bridge-adapters exactly against published 2.11.7 - #868

Merged
rmcdaniel merged 1 commit into
mainfrom
rust-325-bridge-exact
Oct 29, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
rust-325-bridge-exact

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Part of #325. Follows #867.

What changes

Published 2.11.7 gives the intended answers at both of bridge-adapters' published-defect steps:

So the published-defect answers of 2.11.1 to 2.11.5 are no longer accepted:

  • the fixture drops published_defects;
  • the contract compares every step exactly;
  • the stored contract observation is the 2.11.7 recording;
  • the unit test now refuses the old answers.

The other four fixtures with published-defect tolerances keep them. 2.11.7 still gives the published answers there: cancellation-scopes, record-local-activity, workflow-import (#765) and worker-sessions.

Local checks

  • The 2.11.7 survey recording of bridge-adapters equals the fixture's expected exactly. The new stored observation differs from the old one only at the five defect steps.
  • bridge-adapters passes the exact contract on a 2.11.7 harness and on native (built from Rust #325: move the parity reference to published Server 2.11.7 #867's head), and compare accepts the pair.
  • Node unit suite: 6366 pass. The one failure is the PhpImageContextTest local false failure, which fails the same way on a clean main checkout here.

🤖 Generated with Claude Code

Published 2.11.7 accepts and deduplicates a bridge update to an
SDK-worker workflow (#747) and refuses a start for an instance another
namespace holds as unavailable (#777). The fixture no longer carries the
published-defect answers of 2.11.1 to 2.11.5, the contract compares every
step exactly, and the stored observation is the 2.11.7 recording.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

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.

1 participant