Skip to content

Conversation

@jor2
Copy link
Member

@jor2 jor2 commented Sep 30, 2025

Description

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@jor2 jor2 self-assigned this Sep 30, 2025
@jor2 jor2 requested review from iamar7 and shemau as code owners September 30, 2025 19:17
@jor2
Copy link
Member Author

jor2 commented Sep 30, 2025

/run pipeline

@toddgiguere toddgiguere merged commit 25aa44a into main Sep 30, 2025
2 checks passed
@toddgiguere toddgiguere deleted the dropdown-vals branch September 30, 2025 20:19
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 2.3.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ocofaigh
Copy link
Contributor

ocofaigh commented Oct 1, 2025

Hmm, I would went with the option to specify an actual value instead of not set - pick the current latest (or ICD default)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants