New release template

Conversation 0 Commits 3 Files Changed 1

+125 -77

3 Commits

Author	SHA1	Message	Date
Djeex	ca4240c84a	Link each commit in the release changelog to its own commit page CI / build-and-scan (pull_request) Successful in 1m13s Details COMMIT_LIST only rendered the bare subject line per commit, with no way to jump to that specific commit — only the triggering commit (Source:) had a link. Each line now reads "- [<short-sha>](<repo>/commit/<sha>) <subject>", matching the same link style already used for Source.	2026-08-23 23:20:39 +02:00
Djeex	83d2dc7ee6	Match adguard-cidre's current template exactly (post 2026-08-23 update) adguard-cidre switched its release changelog from a changed-files list to a commits list (with --- dividers) after the previous commit here was written from an already-stale read of that file. Also drops the glob-based smoke test (never actually part of the real template, only of nvidia-stock-bot's own drift) for an explicit per-file check matching the canonical error-handling shape, and aligns the remaining step names/commit message wording.	2026-08-23 23:09:35 +02:00
Djeex	8f4d763048	Align CI release workflow with the adguard-cidre/nvidia-stock-bot template Pin Trivy to 0.74.0 instead of latest, make the deprecation check non-blocking (warning only), log the release API's HTTP status code so a failure is actually visible in the CI logs, drop the redundant Docker socket mount on the Trivy steps, and switch the version-bump push to the same URL-embedded-token approach and extraheader key the other repos use. Also generalizes the smoke test to every top-level .py file instead of a hardcoded list, and enriches the release body (changelog header, source links, changed files) to match the other repos' output. Adds the weekly Monday 6am schedule trigger too, so a Trivy scan still runs even on a week Renovate finds nothing to bump.	2026-08-23 22:47:27 +02:00

Author

SHA1

Message

Date

Djeex

ca4240c84a

Link each commit in the release changelog to its own commit page

CI / build-and-scan (pull_request) Successful in 1m13s

Details

COMMIT_LIST only rendered the bare subject line per commit, with no
way to jump to that specific commit — only the triggering commit
(Source:) had a link. Each line now reads
"- [<short-sha>](<repo>/commit/<sha>) <subject>", matching the same
link style already used for Source.

2026-08-23 23:20:39 +02:00

Djeex

83d2dc7ee6

Match adguard-cidre's current template exactly (post 2026-08-23 update)

adguard-cidre switched its release changelog from a changed-files list
to a commits list (with --- dividers) after the previous commit here
was written from an already-stale read of that file. Also drops the
glob-based smoke test (never actually part of the real template, only
of nvidia-stock-bot's own drift) for an explicit per-file check
matching the canonical error-handling shape, and aligns the remaining
step names/commit message wording.

2026-08-23 23:09:35 +02:00

Djeex

8f4d763048

Align CI release workflow with the adguard-cidre/nvidia-stock-bot template

Pin Trivy to 0.74.0 instead of latest, make the deprecation check
non-blocking (warning only), log the release API's HTTP status code so
a failure is actually visible in the CI logs, drop the redundant
Docker socket mount on the Trivy steps, and switch the version-bump
push to the same URL-embedded-token approach and extraheader key the
other repos use. Also generalizes the smoke test to every top-level
.py file instead of a hardcoded list, and enriches the release body
(changelog header, source links, changed files) to match the other
repos' output.

Adds the weekly Monday 6am schedule trigger too, so a Trivy scan still
runs even on a week Renovate finds nothing to bump.

2026-08-23 22:47:27 +02:00

New release template #30