Skip to content

fix: clarify usage of H3 headers in changelog section structure #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 2, 2025

Conversation

virgofx
Copy link
Member

@virgofx virgofx commented Jun 2, 2025

This should help ensure release notes generated using gpt-4.1 are more closely aligned with the instructions.

This should help ensure release notes generated using gpt-4.1 are
more closely aligned with the instructions.
Copy link

github-actions bot commented Jun 2, 2025

Release Plan

Module Release Type Latest Version New Version
tf-modules/kms initial v1.0.0
tf-modules/s3-bucket-object initial v1.0.0
tf-modules/vpc-endpoint initial v1.0.0

Changelog

tf-modules/kms/v1.0.0 (2025-06-02)

  • 🔀PR #218 - fix: clarify usage of H3 headers in changelog section structure

tf-modules/s3-bucket-object/v1.0.0 (2025-06-02)

  • 🔀PR #218 - fix: clarify usage of H3 headers in changelog section structure

tf-modules/vpc-endpoint/v1.0.0 (2025-06-02)

  • 🔀PR #218 - fix: clarify usage of H3 headers in changelog section structure

Wiki Statusℹ️

✅ Enabled

Automated Tag Cleanupℹ️

⏸️ Existing tags and releases will be preserved as the delete-legacy-tags flag is disabled.

Powered by:   techpivot/terraform-module-releaser

Copy link

sonarqubecloud bot commented Jun 2, 2025

@virgofx virgofx merged commit 73b9330 into main Jun 2, 2025
26 checks passed
@virgofx virgofx deleted the improve-release-notes-formatting-2025-06-01 branch June 2, 2025 03:06
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.

1 participant