Skip to content

Fix release titles/notes and close leftover Trivy S3 alerts - #16

Merged
eschultink merged 1 commit into
mainfrom
s232-release-tool-improvements
Aug 20, 2026
Merged

Fix release titles/notes and close leftover Trivy S3 alerts#16
eschultink merged 1 commit into
mainfrom
s232-release-tool-improvements

Conversation

@eschultink

Copy link
Copy Markdown
Member

Summary

  • Release workflow was using github.ref (refs/tags/v1.0.0) as the tag and title; it now uses the tag name and CHANGELOG-based notes (features / fixes / breaking changes, no Contributors section).
  • v1.0.0 added optional versioning and logging, but Trivy still flags the bucket because those resources are count = 0 at defaults. Ignore AVD-AWS-0090 / AVD-AWS-0089 the same way encryption is ignored, and skip scanning examples/ so the registry copy is not reported twice.

Fixes

Code scanning alerts that should close after this lands on main and Trivy re-uploads SARIF:

Change implications

  • dependencies added/changed? no

Test plan

  • Confirm a dry run of scripts/generate-release-notes.sh v1.0.0 emits Breaking / Features / Changes and no Contributors
  • After merge, confirm the Trivy workflow SARIF upload closes the four alerts above
  • Spot-check README / examples/basic-remote now pin ~> 1.0.0

Made with Cursor

Use the tag name (not github.ref) and CHANGELOG-based notes so releases are not titled refs/tags/... with stock What's Changed. Ignore opt-in versioning/logging checks that Trivy still flags at module defaults.

Co-authored-by: Cursor <cursoragent@cursor.com>
@eschultink eschultink self-assigned this Aug 17, 2026
@eschultink
eschultink enabled auto-merge (squash) August 19, 2026 18:29
@eschultink
eschultink merged commit 445817a into main Aug 20, 2026
17 checks passed
@eschultink
eschultink deleted the s232-release-tool-improvements branch August 20, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants