release-verify

Release verification validates that a specific Git tag resolves to a commit, confirms GitHub workflow conclusions, and checks that npm packages and GitHub Release assets align with the target version.

End-to-end release verification includes validating tag existence, checking that Publish npm Package and Release APK workflows completed successfully, confirming GitHub Release assets, and verifying npm publication for the target version.

You can check latest.json accuracy and immutable APK URLs by running a verification script that confirms latest.json points to the requested version and validates that artifact URLs and SHA256 checksums align correctly.

Yes, you need git, gh CLI, curl, node, npm, and awk installed in your environment to run the release verification script, as it depends on these tools to query repositories, registries, and metadata endpoints.

Yes, you can validate the stable APK redirect and Cloudflare metadata by running the verification script with a target version, which checks that the stable redirect points to the correct release asset.

If GitHub Release assets and npm package versions are not aligning, the verification script will fail its checks, indicating that either the Publish npm Package or Release APK workflow did not complete successfully for that tag.