Repository navigation
Release 8.0.0 - #4453
Open
github-actions[bot] wants to merge 14 commits into
Open
Release 8.0.0#4453github-actions[bot] wants to merge 14 commits into
github-actions[bot] wants to merge 14 commits into
Conversation
…, browser-sdk 8.0.0, agent-sdk 8.0.0)
Contributor
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — The diff adds only release metadata and does not change library runtime code, but the required validation evidence is incomplete: several checks were skipped and the repository Lint and Test checks failed. Human review is therefore needed before merging. Not approved because:
No code changes detected at Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more. |
# Conflicts: # .github/workflows/npm-publish.yml # .github/workflows/push-release-tag.yml # dev/tests/test_release_push.py
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 8.0.0
This PR was created by the Create Release Branch workflow.
Checklist
RC1 passed the Release workflow at source
34e6d361aeae2b4f7eee96c4d3359ed2f2c15b0d. Node, Browser, Agent, Android, iOS, and the backend are public at8.0.0-rc1. Public package archives and registry metadata are verified. The backend image contains Linux amd64 and arm64. All six installed Node package platform tests passed. The RC docs are merged in #4450 and deployed.Branch update (2026-10-14)
This PR now targets
main, andmainis merged into the branch (b6b4d3291e). The release workflow fixes that were made on this branch are already onmain:ff6109b5e0(#4456 and the npm tag fixes) landed them, and later commits hardened them further. The merge keptmain's version ofnpm-publish.yml,push-release-tag.yml, anddev/tests/test_release_push.py. The PR diff is now onlydocs/release-notes/release-8.0.0.json.Checked on the merged tree:
check-release-push, then checks out, builds, publishes, and tags that SHA. Version classification still uses the requested ref.npm-publishchecks that HEAD and the prepared tag match the source SHA, and pushes the tag in the separatepush-release-tagjob.push-release-tagaccepts all six SDKs.dev/tests/test_release_push.pyanddev/tests/test_ci_suites.pypass (28 tests).sourceCommitis on this branch.Note
Rework release workflows to resolve source SHA in preflight and isolate tag pushes
Adds a shared preflight job to all SDK release workflows (node, browser, agent, CLI, iOS, Android). The preflight resolves the requested ref to a commit SHA; setup, build, and publish jobs then check out that fixed SHA, and version classification still uses the requested ref.
push-release-tagjob instead of from the publish job.node-sdk,browser-sdk,agent-sdk, andcli.dry-runinput that skips GitHub App token creation.Macroscope summarized d94bf17.