-
Couldn't load subscription status.
- Fork 0
fix: clean up legacy catalog modules #704
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
Conversation
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this line too
terraform-ibm-kms-key-ring/.releaserc
Line 12 in 209c3b0
| "successCmd": "echo \"SEMVER_VERSION=${nextRelease.version}\" >> $GITHUB_ENV" |
|
/run pipeline |
| "assets": "false" | ||
| }], | ||
| ["@semantic-release/exec", { | ||
| "successCmd": "echo \"SEMVER_VERSION=${nextRelease.version}\" >> $GITHUB_ENV" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah very sorry @shemau This line is correct and should be there. The command to trigger pipeline was already removed from the repo
|
/run pipeline |
|
🎉 This PR is included in version 2.6.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Remove legacy module catalog entries that now conflict (see #701) with pipeline validation code.
Includes a bump to the latest common-dev-assets to validate that it resolves the issue in #701.
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers