Skip to content

chore: merge main into feature branch - #242

Merged
3 commits merged into
feature/dungdongfrom
main
Nov 18, 2026
Merged

3 commits merged into
feature/dungdongfrom
main

Conversation

@dungdong-aws

Copy link
Copy Markdown
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.

Send `awsClientCapabilities.q.workspaceTrust` at initialize and
`aws/updateConfiguration` (`aws.q.workspaceTrust`) when VS Code grants
trust, so the language server starts local MCP servers only in trusted
workspaces.
…237)

* fix(amazonq): read developer override settings from user settings only

* fix(amazonq): scope packaged developer settings

* fix(amazonq): use extension mode for dev overrides

* fix(amazonq): defer developer settings until activation

* fix(amazonq): own developer settings lifecycle

* fix(amazonq): scope developer settings in manifest
* Release 2.10.0

* Update version to snapshot version: 2.11.0-SNAPSHOT

---------

Co-authored-by: aws-toolkit-automation <>
@dungdong-aws
dungdong-aws requested a review from a team as a code owner November 18, 2026 18:02
@dungdong-aws dungdong-aws closed this pull request by merging all changes into feature/dungdong in e340966 Nov 18, 2026
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.

1 participant