chore: modify how changelog is generated

[seqre]

Changes to the config:

• do not generate changelog for cot-codegen and cot-macros
• extract security changes to separate category
• preprocess commit messages to include links, so that the changelog is useful outside of GitHub
• removed pointless comments
• always output breaking commits

With those changes, the changelog for this version for cot will look like this:

0.2.0 - 2025-03-18

Security

• cycle session ID on login, flush session on logout (#246)

New features

• add a user-friendly message for AddrInUse error (#233)
• add support for remove field in automatic migration generator (#232)
• add basic pagination support for admin panel (#217)
• support "Remove Model" in Automatic Migration Generator (#221)

Fixes

• panic backtrace/location not displayed on the error page (#237)
• include APP_NAME in model (#228)

Other

• [breaking] upgrade edition to 2024 (#244)
• (clippy) add --all-targets to clippy CI and fix all warnings (#240)
• add test for reverse!() reversing in the current app first (#239)
• more docs (up to 100% doc coverage) (#229)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
rust	81.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[m4tx]

Should we also remove the already existing changelogs for cot-codegen and cot-macros?

[seqre]

Should we also remove the already existing changelogs for cot-codegen and cot-macros?

There are none on master or I'm blind. The ones in the release PR should (I hope) disappear once release-plz reruns with that config. If not, we can delete them from there.

[seqre]

Should we also remove the already existing changelogs for cot-codegen and cot-macros?

There are none on master or I'm blind. The ones in the release PR should (I hope) disappear once release-plz reruns with that config. If not, we can delete them from there.

Yup, that's what happened @m4tx: https://github.com/cot-rs/cot/pull/215/files