[crandmck]

Summary

Stacked node-only follow-up to #265. Reuses its generic documentation version updater and existing single full-site build/deployment.

• Select stable @contentauth/c2pa-node versions from Changesets publication outputs and add the node release.published fallback.
• Verify the exact GitHub release metadata and npm version, promote/deduplicate api-docs/node-versions.json while preserving history and metadata, and persist only that index directly to main before deployment.
• When web and node publish together, update each package's index before one complete-site build/deployment. Node-only publication never changes the web index.
• Preserve native-binary rebuild inputs, npm publication, main/manual complete docs rebuilds, and prerelease Changesets docs rebuilds; prereleases are not automatically added.

Validation

• pnpm test:docs: 36 passing tests, including actual workflow selection/persistence shell executed against local bare Git remotes for web-only, node-only, and combined publication, index-only commits, rerun no-op, rejected pushes, invalid metadata, and missing/mismatched npm publication.
• pnpm ci:docs:releases: both node and web versioned sites built successfully from published npm declarations.
• Targeted ESLint, workflow/test Prettier checks, Ruby YAML parsing, and git diff --check passed.
• Inherited docs: Update web API versions after stable releases #265 head verified at 4575c70d6a2f49e8c8c2f89a24c6223bd7f614d1; no changes to its branch or PR.

Activation caveat

Direct bot commits to main require repository permissions/rules to permit them. Current review/code-owner protection will otherwise reject the push and stop deployment. This change does not configure or bypass protection. Development pushed only this implementation branch, not main or tags. Live release publication and GitHub Pages deployment were not exercised locally.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8db7327

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ale-adobe]

Is this part still true with the new automation?