Skip to content

Conversation

@tsmithsz
Copy link
Contributor

Problem

Solution


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@tsmithsz tsmithsz requested a review from a team as a code owner August 29, 2025 18:29
@amazon-inspector-ohio
Copy link

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

@amazon-inspector-ohio
Copy link

✅ I finished the code review, and didn't find any security or code quality issues.

@tsmithsz tsmithsz changed the title Release 1.92.0 fix: release 1.92.0 Aug 29, 2025
@tsmithsz tsmithsz force-pushed the add-release-1.92.0-commit branch from 0c72846 to 23b8c0e Compare August 29, 2025 18:34
@tsmithsz tsmithsz changed the title fix: release 1.92.0 fix(amazonq): release 1.92.0 Aug 29, 2025
@tsmithsz tsmithsz force-pushed the add-release-1.92.0-commit branch from 23b8c0e to ec1c9e9 Compare August 29, 2025 18:35
@tsmithsz tsmithsz changed the title fix(amazonq): release 1.92.0 fix(amazonq): bump version to 1.93.0-SNAPSHOT Aug 29, 2025
@tsmithsz tsmithsz merged commit b9ce873 into aws:master Aug 29, 2025
31 checks passed
@tsmithsz tsmithsz deleted the add-release-1.92.0-commit branch August 29, 2025 19: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.

3 participants