Skip to content

Conversation

@PeterSchafer
Copy link
Contributor

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

@PeterSchafer PeterSchafer requested a review from a team as a code owner July 21, 2025 13:58
@PeterSchafer PeterSchafer changed the base branch from main to release-candidate July 21, 2025 13:58
@snyk-io
Copy link

snyk-io bot commented Jul 21, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

@github-actions
Copy link
Contributor

Warnings
⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 2ca7404

@PeterSchafer PeterSchafer enabled auto-merge July 21, 2025 14:01
@PeterSchafer PeterSchafer merged commit 9360711 into release-candidate Jul 21, 2025
8 checks passed
@PeterSchafer PeterSchafer deleted the fix/CLI-1015_incorrect_version branch July 21, 2025 14:52
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.

3 participants