chore(release): v2.0.39

[khaliqgant]

Why

Release run 37102722961 published relayflows, @relayflows/sdk, @relayflows/surface, @relayflows/runtime-linux-x64 and @relayflows/runtime-darwin-arm64 at 2.0.39 (all verified on npm). Its last step, "Commit version bump and create tag", then failed:

! [rejected]          HEAD -> main (fetch first)
error: atomic push failed for ref refs/heads/main

#501 merged to main at 06:25:30Z while the release (dispatched 06:20Z from 731567a) was running. So main still declares 2.0.38 and there is no v2.0.39 tag. The next patch release would compute 2.0.39 again and fail to publish.

What

The same eight-file bump the workflow makes, matching the v2.0.38 release commit (30b0565) file for file: package versions, cross-package dependency pins, and the lockfile version/resolved/integrity entries. Integrity hashes are read from the published 2.0.39 tarballs (npm view @relayflows/<pkg>@2.0.39 dist.integrity), not computed locally. No 2.0.38 remains in these files.

After merge

Tag the merge commit v2.0.39 (annotated, "Release v2.0.39"), as the workflow would have. I'll do that once this merges.

Humans merge this repo.

🤖 Generated with Claude Code

---

Summary by cubic

Syncs main to the published 2.0.39 packages so the next release doesn't try to publish 2.0.39 again.

• The v2.0.39 release published all five packages to npm but its final version-bump push was rejected because main moved mid-release (Harden agent transport recovery and diagnostics #501 merged at 06:25:30Z).
• Applies the same eight-file version bump the workflow would have generated: package versions, cross-package dependency pins, and lockfile version/resolved/integrity entries, with integrity hashes read from the published 2.0.39 tarballs.
• After merge, tag the merge commit v2.0.39 (annotated) as the workflow would have.

^{Written for commit caf1db9. Summary will update on new commits.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-03T06:35:50.967222Z	caf1db9	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: bebdd0e8-39f5-40ce-bdd6-6e2154648d43

📥 Commits

Reviewing files that changed from the base of the PR and between f6b8290 and caf1db9.

⛔ Files ignored due to path filters (3)

• packages/relayflows/package-lock.json is excluded by !**/package-lock.json
• packages/sdk/package-lock.json is excluded by !**/package-lock.json
• packages/surface/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• packages/relayflows/package.json
• packages/runtime-darwin-arm64/package.json
• packages/runtime-linux-x64/package.json
• packages/sdk/package.json
• packages/surface/package.json

 _______________________________________________________
< I find bugs faster than you can say 'merge conflict.' >
 -------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[cubic-dev-ai]

No issues found across 8 files

_{Re-trigger cubic}