chore(release): 1.1.0

[paulosfjunior]

Prepares the 1.1.0 release: closes [Unreleased], moves every copy-paste reference in the documentation, and adds the guard that stops those references from drifting again.

Why 1.1.0 and not 2.0.0

No input, default or behaviour of the component changed. The only consumer-visible item is the runner floor introduced by #4 and #5: actions/upload-artifact@v6+ requires Actions Runner ≥ 2.327.1 on self-hosted runners. That runner shipped in mid-2025 and GitHub self-hosted runners auto-update, so a runner below it is already outside GitHub's own support. Recorded prominently in CHANGELOG.md and SUPPORTED-INTEGRATIONS.md rather than signalled with a major bump that would force every consumer to edit @v1 → @v2.

The new guard: check-sync.sh section 4

21 copy-paste references still said v1.0.0 — the quick start in both READMEs, all of examples/, the onboarding guide and SUPPORTED-INTEGRATIONS.md. Nothing checked them. The repository already refuses to let the scanner image pin drift from VERSION; the component version in the docs had no equivalent, so every release could silently leave the quick start teaching the previous tag.

Section 4 matches only the three forms a reader actually copies:

ci-security-scanner@vX.Y.Z
ci-security-scanner/vX.Y.Z/          (remote include URL)
ci-security-scanner/<component>@X.Y.Z (catalog)

Prose explaining the tagging scheme — "v1.0.0 is never moved", the floating-tag table — is illustrative and deliberately not matched.

Verified it fails as well as passes:

FAIL examples/github/security-scan.yml pins 1.0.0, expected 1.1.0  (ci-security-scanner@v1.0.0)
1 check(s) failed          exit=1

Onboarding guide URL corrected

The organization serves Pages from a custom domain, so tooark.github.io/ci-security-scanner/ is a 301. Canonical address is https://tooark.com/ci-security-scanner/ — now live, and used in both READMEs, SUPPORT.md, CONTRIBUTING.md, the issue-form chooser and the workflow header.

Affected area(s)

• VERSION — component version
• scripts/ — validation run in CI and locally
• docs/ · examples/ · governance documentation

Consumer impact

• No consumer-visible change (documents the one made by chore(deps): Bump actions/cache from 4 to 6 #4 and chore(deps): Bump actions/upload-artifact from 4 to 7 #5)

Checklist

• python3 scripts/validate-templates.py passes
• ./scripts/check-sync.sh passes — including the new section 4
• Every .yml parses
• README.md and README.pt-BR.md updated and in sync
• CHANGELOG.md closed at [1.1.0] with compare links
• Scanner image pin untouched (1.9)

After merge: tag v1.1.0, which release.yml validates against COMPONENT_VERSION before publishing and moving v1 / v1.0.

🤖 Generated with Claude Code