[benbrandt]

Summary

Permanently use the checked-in Release Please configuration and manifest.

• Remove the action-level release-type: node input. In the pinned action, providing it selects Manifest.fromConfig and bypasses config-file and manifest-file, inferring the stale 2.0.0 baseline from merged PR chore(main): release 2.0.0 #293.
• Keep the Node release strategy in release-please-config.json and explicitly set include-component-in-tag: false to preserve this repository's existing vX.Y.Z tags. Otherwise manifest mode defaults to sdk-vX.Y.Z and cannot match v1.9.0.

This is permanent configuration, not a temporary recovery mode or a forced version. No further package-version reset is needed.

Read-only release-plan verification

Used release-please 17.6.0, matching the pinned action's bundled dependency, against live GitHub state. Loaded the remote config/manifest in manifest mode and applied the proposed local tag-format setting in memory. The verification used only buildReleases() and buildPullRequests(), with an HTTP guard rejecting mutations.

Verified:

• Configured baseline: 1.9.0.
• Existing release found: v1.9.0, SHA 1db4d43286d993545e729376346b7f9098748159.
• 10 commits considered, rather than 500 historical commits.
• Exactly one proposed PR: chore(main): release 2.0.0.
• Proposed branch: release-please--branches--main--components--sdk, matching chore(main): release 1.0.0 #300.
• Notes compare v1.9.0...v2.0.0, include the legacy API breaking changes, and do not restore the obsolete connector recommendation.
• No merged pending releases would be published on the fix's push, based on the inspected state.

After this PR merges, let Release Please update #300 and inspect that actual proposal and CI before merging it. Do not merge #300 while it still proposes 1.0.0.

Other validation and scope

• npm run format:check and git diff --check passed.
• Parsed workflow YAML and asserted manifest-mode inputs, Node release strategy, and existing unprefixed tag format.
• Publish-job configuration is unchanged, including permissions and steps.
• CI workflow, npm installation policy, SDK code, schemas, package version, lockfile, and version manifest are unchanged.
• Runtime tests were not rerun for this configuration-only change. No repository tests/docs were added.

No GitHub releases/tags, generated PR branches, or npm publications were changed by the verification. No workflow reruns were triggered.