Skip to content

revert: release - #177

Closed
laileni-aws wants to merge 2 commits into
Amazon-Q-Developer:mainfrom
laileni-aws:release/2.6.0
Closed

revert: release#177
laileni-aws wants to merge 2 commits into
Amazon-Q-Developer:mainfrom
laileni-aws:release/2.6.0

Conversation

@laileni-aws

Copy link
Copy Markdown
Collaborator

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.

chungjac and others added 2 commits August 20, 2026 21:05
The repo moved from the aws org to Amazon-Q-Developer
(https://t.corp.amazon.com/P484890134).

- CODEOWNERS: the @aws/* teams do not exist in the new org, so every entry
  was an "Unknown owner" and code-owner review could not be satisfied. Collapse
  to @Amazon-Q-Developer/sync-team-dae-production-eng-team (the synced eng team),
  matching what was done for language-servers. Granular per-directory teams have
  no equivalent in the new org yet.
- node.js.yml / notification.yml: `github.repository == 'aws/amazon-q-vscode'`
  guards now evaluate false, silently skipping the Codecov upload and PR
  notification jobs. Repoint to Amazon-Q-Developer/amazon-q-vscode.
…r#174)

* Update third-party license attribution for release/rc-20260819

* Release 2.5.0

* Update version to snapshot version: 2.6.0-SNAPSHOT

---------

Co-authored-by: aws-toolkit-automation <>
@laileni-aws
laileni-aws requested a review from a team as a code owner August 21, 2026 04: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.

3 participants