docs: update changelog for pr validation fallbacks
Some checks failed
Pull Request Validation / validate (pull_request) Successful in 4m34s
Release / prepare (push) Failing after 4s
Push Validation / check-open-pr (push) Successful in 3s
Release / publish (push) Has been skipped
Push Validation / validate (push) Failing after 16s

This commit was merged in pull request #1.
This commit is contained in:
Micheal Wilkinson
2026-03-21 23:02:46 +00:00
parent 2294bb940b
commit 710fe049f5

View File

@@ -37,6 +37,8 @@ A `### Breaking` section is used in addition to Keep a Changelog's standard sect
- Push validation open-PR detection is now POSIX-shell compatible (no bash-only `pipefail`/array/`[[ ... ]]` usage), fixing failures on runners that execute `run` scripts with `/bin/sh`.
- PR validation now checks that `coverage.out` exists before invoking `coverage-badge`; when missing, badge upload is skipped with a summary note instead of failing the workflow.
- PR decoration is now `continue-on-error` to avoid hard-failing validation when the external `decorate-pr` action's internal extractor step is unavailable.
- PR validation now skips external PR decoration on non-GitHub runners and writes a summary note instead, avoiding runner-specific action resolution failures.
- Coverage summary generation is now resilient when badge outputs or `coverage-packages.md` are unavailable, preventing summary-step hard failures after earlier skips.
- README badge link target updated to `actions/runs/latest?workflow=...` format per workflow standards.
- CI security scanning now uses GitHub Marketplace actions (`securego/gosec` and `golang/govulncheck-action`) instead of manual tool installation, improving reliability and caching.
- CI setup compatibility fix: gosec scanner now references the correct public action source (`securego/gosec`), resolving action clone failures in Gitea runners.