Repository navigation
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
Summary
Set up an explicit Node-only
2.0.0-next.0prerelease under npm'snexttag, without merging Node SDK v2 or changing the stable Changesets/docs publisher. This is an automation-only PR based on current main; the candidate remains Node #790, currently0809be2b95f43fa1785c6b7b188c03ac8fd40965.A separate workflow is intentional: GitHub must have the manual workflow on the default branch before dispatch, so this can land independently of the SDK migration and avoid prematurely putting v2 into the normal stable release flow.
Behavior and safeguards
node-sdk-prerelease.yml). No push, tag or PR publication triggers. Defaults to artifact-only (publish=false). Only a dispatch frommaincan publish.2.0.0-next.Nmatching the candidate's existing manifest; no source version rewriting or Changesets prerelease mode.@reflag/node-sdk, and verifies thatworkspace:*resolved to published evaluator 2.0.0. Validates tarball contents/entry points, compiled SDK version metadata and SHA-256/SHA-512 integrity.npm-node-prerelease; candidate code/dependency/lifecycle scripts never run in that job. Preparation has no OIDC permission. Both prerelease jobs explicitly disable dependency caching, preventing candidate checkout from poisoning the default-branch cache scope.publish=truefirst verifies that the GitHub environment already has required reviewers. It fails closed if the environment is absent or unprotected.npm publish <one-tarball> --tag next --access public --provenance --ignore-scripts. No evaluator, OpenFeature, Browser/framework or CLI publication, no Git tags/releases, no docs push, and no general Changesets publish command.next, registry tarball integrity and unchangedlatestafterward, with bounded reads for registry visibility. Does not repair/retag/unpublish anything automatically.test:releaseandprerelease:nodecommands.Validation
0809be2candidate: 271 Node tests, both existing SDK type programs, clean package builds, two strict installed-package consumers and real installed-package HTTP/runtime checks pass.latest: 1.8.3. SHA-256:4e9fc2a58ca995d7aa23717909076422af01e5913739e52edd3c84a4e13a6424..github/workflows/publish.ymland every package source/manifest remain unchanged. Full lint has zero errors and one inherited warning in generated Next.js environment declarations. Normal hooks passed; committed tree matches the verified prepared tree.b6f02cc5da8e8435d06ac4d06e952d2a85d901bd: both complete Build & Test runs (43641143957,43641140252), CodeQL/Analyze and Oneleet pass; PR is MERGEABLE/CLEAN. Initial CodeQL caught a genuine cache-poisoning hazard; the follow-up disables all prerelease-job caching and adds a regression guard, without suppressing the alert. An earlier push run's report-action HTTP 404 is historical and superseded by both passing final runs. No full-repository local rebuild/E2E was claimed; the full rebuild/test jobs ran remotely.Activation still required — nothing published
npm-node-prereleasewith required reviewers. It did not exist at setup inspection; the workflow refuses publication without protection.@reflag/node-sdk: organizationreflagcom, repositoryjavascript, workflow filenamenode-sdk-prerelease.yml, environmentnpm-node-prerelease, with Allow npm publish. Keep the stable publisher intact; no token fallback is added. Configure this close to first use because new npm trusted-publisher entries require their first successful publish within two days.matchedRuleIdpatch remains outside feat(node-sdk): adopt collection values and Boolean-first reads #790 and is not silently included. Server/snapshot/canary readiness and v1 bootstrap incompatibility still apply.publish=trueplus the environment approval.latestmust stay on v1; the first prerelease version must not already exist. Automatic npm provenance identifies the trusted main workflow/build run; the separately selected SDK source SHA is recorded in dispatch inputs, the job summary andcandidate.json. Do not treat the main workflow revision as the SDK candidate commit.After activation, an artifact-only run would be:
No prerelease workflow was dispatched, no npm trusted publisher/environment was created, no package/tag was published or changed, and no main merge, deployment, snapshot rebuild, persistent-service restart or model study occurred during setup. npm/OIDC publication itself remains untested until the explicitly approved first publish.