Version updated for https://github.com/plainproof-labs/release-regression-guard to version v1.1.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary The Release Regression Guard action automates the verification of critical URLs after a deployment by comparing a repository-owned manifest with the deployed origin. It checks for broken redirects, noindex, canonical/metadata regressions, sitemap gaps, and missing internal links. The main functionality is to report these issues in the workflow Job Summary as pass, fail, unknown, or documented temporary exceptions.

Version updated for https://github.com/plainproof-labs/release-regression-guard to version v1.0.1. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 24. Go to the GitHub Marketplace to find the latest changes. Action Summary Release Regression Guard is a GitHub Action that automates SEO checks on deployed pages. It compares repository-declared critical URLs with an expectation manifest, ensuring the site’s content meets SEO requirements after deployment. The action reports each check as pass, fail, unknown, or a documented temporary exception. Key capabilities include verifying final HTTP status and redirects, checking noindex settings, canonical links, metadata presence, sitemap membership, and internal links.

Version updated for https://github.com/plainproof-labs/release-regression-guard to version v1.0.0. This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20. Go to the GitHub Marketplace to find the latest changes. Action Summary Release Regression Guard is a GitHub Action that automates critical URL checks for SEO purposes after deployments. It compares repository-declared URLs against an expectation manifest, reporting pass/fail outcomes with detailed summaries and evidence. The action supports various checks such as HTTP status, same-origin redirects, indexing, canonical URLs, metadata presence, sitemap membership, and internal links. Users can install the Action from a published version or SHA, ensuring robustness and maintainability in their workflows.