chore(main): release 1.3.0

[devsecninja-automation]

🤖 I have created a release beepboop

1.3.0 (2026-05-03)

⚠ BREAKING CHANGES

• mise: Update tool cocogitto ( 6.4.0 ➔ 7.0.0 ) (#43)

Features

• lint: add self lint and auto-fix callers with shared config support (#66) (02a3e49)
• mise: Update tool cocogitto ( 6.4.0 ➔ 7.0.0 ) (#43) (b6a0cad)
• mise: update tool git-cliff ( 2.8.0 ➔ 2.12.0 ) (#38) (085b778)
• mise: update tool trivy ( 0.69.3 ➔ 0.70.0 ) (#48) (81a5c41)

Bug Fixes

• github-release: update release jdx/mise ( v2026.4.9 ➔ v2026.4.17 ) (#28) (1937cb6)
• mise: update tool lefthook ( 2.1.4 ➔ 2.1.6 ) (#21) (ae88aec)
• mise: update tool pipx:checkov ( 3.2.521 ➔ 3.2.522 ) (#73) (2b1bf6c)
• notify-irm: remove ${{ }} templates from description blocks (#53) (b250963)
• renovate: pin Renovate version ranges by default (#70) (1cf2a9c)
• update title in bug_report.md (a3db2f9)
• update title in feature_request.md (acdef53)
• workflows: exclude Renovate issues from codeowner assignment (2ad05e7)

Miscellaneous Chores

• release 1.2.0 (7c98ece)
• release 1.3.0 (2e2c691)

---

This PR was generated with Release Please. See documentation.

[DevSecNinja]

@copilot I don't want to release a 2.0.0. I have fixed the Renovate majors that from now on they will not be pushed as breaking. Can you do this: https://github.com/googleapis/release-please#how-do-i-change-the-version-number

[Copilot]

@copilot I don't want to release a 2.0.0. I have fixed the Renovate majors that from now on they will not be pushed as breaking. Can you do this: https://github.com/googleapis/release-please#how-do-i-...

Done in commit 2d807a9. Updated .release-please-manifest.json to 1.3.0 and updated CHANGELOG.md accordingly — removing the breaking changes section and updating all 2.0.0 references to 1.3.0.

[devsecninja-automation]

🤖 Created releases:

• v1.3.0

🌻