release-update-published-version

Automate post-release version updates by running a script that syncs docs home page badges, version references, and site assets after npm and GitHub releases go live. It regenerates build outputs and commits the changes to prevent version drift.

The safest way to sync release-facing docs is to enforce validation checks ensuring the target version exists on both npm and GitHub Releases before applying changes and committing updates to public-facing surfaces.

Prevent version drift by automating the update of version references across docs and sites directories, which regenerates and commits built artifacts to keep the public site synchronized with the latest release.

Yes, you can use this automation to update version badges on the docs home page and regenerate release-facing artifacts such as built docs and stage outputs, ensuring public surfaces reflect the latest version.

You do not need to manually verify releases because the script implements safety checks that validate the target version exists on both npm and GitHub Releases before applying any changes.

The release update script fails because it enforces safeguards that require the target version to be successfully published on both npm and GitHub Releases before applying any documentation or asset updates.