…or agentic chat (#7857)

## Problem
In order to set appropriate Origin Info on LSP side for SMAI CodeEditor,
[link](https://github.com/aws/language-servers/blob/68adf18d7ec46a7ecf9c66fd9d52b1b8f7bc236e/server/aws-lsp-codewhisperer/src/shared/utils.ts#L377),
clientInfo needs to be distinct
- related [PR to support
SMUS](#7817)

## Solution
- To check if the environment is SageMaker and a Unified Studio instance
and set corresponding clientInfo Name which is ```AmazonQ-For-SMUS-CE```

## Testing
- Built artefact locally using ```npm run compile && npm run package```
and tested on a SMAI CE space
- Ran ```npm run test -w packages/toolkit``` which succeeded
- LSP logs show the respective client Info details
```

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

Co-authored-by: Laxman Reddy <[email protected]>

…7839)

## Problem
Inline completion suggestions were being shown even when edit
suggestions were active, creating a confusing user experience where both
types of suggestions could appear simultaneously.

## Solution
1. Added conflict prevention logic in provideInlineCompletionItems() to
check for active edit suggestions using the existing
aws.amazonq.editSuggestionActive context flag
1. Created isEditSuggestionActive() method to encapsulate context
checking
1. Implemented DISCARD telemetry for completion suggestions that can't
be shown due to active edits
1. Added unit tests covering the new functionality, including edge cases
for mixed suggestion types and items without IDs
1. Updated displayImage.ts to properly set/unset the context flag when
edit suggestions are displayed/cleared
1. The solution ensures only one type of suggestion is active at a time
while maintaining telemetry compliance and following existing codebase
patterns.

---
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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

**Description**

Added credential providers for DER, Project role credentials and
Connections credentials. Added in memory caching for now.

The credential providers currently are structured so that it can be used
with CredentialStore but a lot of things to do with credential store is
really old. In the coming days, while we do bug bashes and tests, if the
in memory caching fares well enough, will simplify the credential
provider to implement the AWS SDK CredentialProvider directly.


**Motivation**

Support auth for SMUS and ensure all clients get credentials and don't
fail due to lack of credentials.

**Testing Done**

Updated unit tests and tested flow locally. 

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Bhargava Varadharajan <[email protected]>

## Problem
The AWS Toolkit VSCode project lacked a streamlined release candidate
workflow. Creating release candidates would require manual branch
creation and version management.

## Solution

Added automated release candidate support:

- Created `.github/workflows/setup-release-candidate.yml `- Workflow to
create RC branches with automatic version bumping

- Supports `Major/Minor/Patch/Custom` version increments

- Reads and increments both `toolkit` and `amazonq` package versions
independently

- Creates date-based RC branches (`rc-YYYYMMDD`)

- Commits version changes and pushes the RC branch

- Updated `.github/workflows/release.yml` - Added support for `release/*
` branches

- Automatically creates `rc-*` prefixed releases for release candidate
branches

- Proper release naming for RC artifacts

This enables a clean RC workflow: trigger the setup workflow with a
commit ID and version increment type, then the release pipeline
automatically handles the rest.



---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
The release candidate workflow was failing with "protected branch update
failed" error because the default `GITHUB_TOKEN ` did not exist.

## Solution

Updated the workflow to use `RELEASE_CANDIDATE_BRANCH_CREATION_PAT`
instead of `GITHUB_TOKEN` in the checkout step.


---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

…es away (#7868)

## Problem

Amazon Q edit suggestions remain active even when users navigate far
away from the suggestion location, leading to confusion and potential
unintended edits when users accept suggestions they can no longer see.

## Solution

Added automatic rejection of edit suggestions when the cursor moves more
than 25 lines away from the suggestion location. Implemented cursor
change listener with proper cleanup to prevent memory leaks and ensure
suggestions are only accepted when contextually relevant.

Fixed 2 failing recommendationService.test.ts tests

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
The prerelease workflow is configured to run on branches matching
release/*. The RC creation workflow previously created branches like
`rc-YYYYMMDD` instead of `release/rc-YYMMDD`, which did not match the
trigger pattern, meaning the prerelease workflow was never invoked
automatically.

As it stands now any team member with write access can perform
workflow_dispatch injection.


## Solution

Update the RC creation workflow to create branches in the format
`release/rc-YYYYMMDD` instead of `rc-YYYYMMDD`, ensuring they match the
prerelease workflow’s `release/*` branch trigger and are picked up for
prerelease builds.

 Sanitize the input fields via Github environment variables

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
SMUS users need Project Space management functionality

## Solution

- Add SageMakerUnifiedStudioSpaceNode for individual space
representation
- Add SageMakerUnifiedStudioSpacesParentNode for space container
management
- Add SagemakerSpace class for unified space operations and status
management
- Enhance SageMaker credential mapping with SMUS project support
- Add space-specific icons and detached server credential resolution
- Update SageMaker commands and model types for space functionality
- Added test cases.
---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.


###Note: Due to lot of constriants - I apologies that I had to raise
such a big PR.

Co-authored-by: guntamb <[email protected]>

## Problem
We only need to create the branch. The bumping of the version will be
handled by the release pipeline scripts.

See github scripts under:
[github.com/aws/aws-toolkit-vscode/tree/master/buildspec/release](https://github.com/aws/aws-toolkit-vscode/tree/master/buildspec/release)

- `10changeversion.yml`: Removes `-SNAPSHOT` from version and creates
git release tag

- `40pushtogithub.yml`: Bumps to next development version with
`-SNAPSHOT` suffix and pushes to GitHub

- `50githubrelease.yml`: Creates official GitHub release with `.vsix`
files and SHA384 hashes

## Solution
Remove the logic to bump the version

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem

The inline completion in Jupyter Notebook is not working.
https://github.com/aws/aws-toolkit-vscode/pull/7086/files is gone after
inline completion migration to language server.

## Solution

1. Re-implement inline completion in Notebook
2. Re-organize the left and right context given precise cursor position
in current cell.

Requires aws/language-servers#2114

<img width="723" height="429" alt="Screenshot 2025-08-12 at 4 09 28 PM"
src="https://github.com/user-attachments/assets/8335360b-7a83-431c-b967-0547cb60a48a"
/>


---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

…d Studio data explorer (#2183)

## Problem
Need to implement Lakehouse nodes and Redshift nodes for SageMaker
Unified Studio data explorer


## Solution
1. Implemented GlueClient and Lakehouse nodes
2. Retrieved all results from pagenation at once
3. Updated node icons and label based on UX requirements
4. Addressed open comments from previous PR:
aws/aws-toolkit-vscode-staging#2182
5. Added and updated unit tests

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Zulin Liu <[email protected]>

__Description:__
Add 2 folder nodes under compute node to list Redshit and Spark
connections.
Add tooltip for the listed connections to show critical information.

## Appearance:
<img width="360" height="304" alt="image"
src="https://github.com/user-attachments/assets/4cb3ca4c-14d2-4373-af1d-35147238895b"
/>

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem

- remove unnecessary files from buildspec

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

… telemetry (#7893)

## Problem
Language server is using
`initializeParams.initializationOptions?.aws?.clientInfo?.version`

https://github.com/aws/language-servers/blob/main/server/aws-lsp-codewhisperer/src/shared/telemetryUtils.ts#L99-L100

However current we're passing IDE version (vscode) and use the other
field as plugin version which is not used by server.

```
clientInfo: {
                    name: getClientName(),
                    version: version,
                    extension: {
                        name: 'AmazonQ-For-VSCode',
                        version: extensionVersion,
```


## 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem

Newly created running Spaces do not have any controls (Stop/Connect)
BugBash: https://quip-amazon.com/c9u0AeXRbgx9/Local-IDE-Bug-Bash
## Solution

show the stop button when the remote connect status is undefined 

## Appearance
note: test3 is a newly created space with remote connect status ==
undefined

<img width="1085" height="418" alt="Screenshot 2025-08-14 at 11 23
19 AM"
src="https://github.com/user-attachments/assets/9b0d150b-2475-4b0e-b214-a37373e0edad"
/>

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem

There is an issue we suspect is related to the recent support we added
for proxy auto-discovery on this GitHub issue:
#7878

## Solution
Disabling the experimental proxy support

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

 Please enter the commit message for your changes. Lines starting

…d bug fixes (#2196)

## Problem
This PR addressing following problems:
1. Handle rendering s3 access grant node
2. Implement client store to create separate clients for different
connections
3. Fix rendering s3 table catalog in Lakehouse node
4. Wire connection credentials provider and bug fixes
5. Adapt connection credentials provider for private model clients
(sqlworkbench, gluecatalog)
6. UX: move all s3 nodes under "Buckets" folder

Rev 2:
1. Addressed comments
2. bug fixes

## Solution
1. Handle rendering s3 access grant node
`createS3AccessGrantNodes` in `sagemakerUnifiedStudioDataNode.ts` and
`s3Strategy.ts`

3. Implement client store to create separate clients for different
connections
`src/sagemakerunifiedstudio/shared/client/clientStore.ts`

4. Fix rendering s3 table catalog in Lakehouse node
`src/sagemakerunifiedstudio/explorer/nodes/lakehouseStrategy.ts`

5. Wire connection credentials provider and bug fixes
Involving all strategy files and client files

6. Adapt connection credentials provider for private model clients
(sqlworkbench, gluecatalog)
`src/sagemakerunifiedstudio/shared/client/credentialsAdapter.ts`

7. UX: move all s3 nodes under "Buckets" folder
`src/sagemakerunifiedstudio/explorer/nodes/s3Strategy.ts`

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Zulin Liu <[email protected]>

…ere setting is not registered (#8343)

## Problem
When the extension is upgraded and user does not do a full restart, it
is possible for new cloudformation telemetry setting to not be
registered yet, resulting in error trying to save it.

## Solution
Skip the save and do it the next time the extension starts.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Akila Tennakoon <[email protected]>
Co-authored-by: manodnyab <[email protected]>

## Problem
Stacks remained in panel as REVIEW_IN_PROGRESS status after ChangeSet
was deleted due to the lack of refresh.

## Solution
Refresh stacks after change set deletion. On create change sets, this
would clear out the stack from panel.

Removing some dead code as well. Since view/delete change set is
disabled from command palette the `params` would never be undefined.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
- replacement may produce '&' characters that are double-unescaped

## Solution
- change the order of the .replace() calls in the decoding of both wsUrl
and token such that & is decoded after all other HTML entities have
been decoded

- Addressing bot suggestion in
#8341

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem

## Solution
Disable log --tail in non snap start functions


---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

…g outFile auto detection (#8366)

## Problem
TS remote debugging on windows was failing due to windows file pattern
is malformed for glob pattern
TS remote debugging on windows can't correctly apply sourceMapOverrides

## Solution
Fixed issues above and not TS debug can successfully work on every OS

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

build(amazonq): merge release candidate version rc-20251125

…staller (#8364)

Ensures we have visibility into LSP version selection/installation
if/when customers report installation related issues.

```
2025-11-24 17:58:10.530 [info] awsCfnLsp: Found CloudFormation LSP provider: RemoteLspServerProvider
2025-11-24 17:58:11.078 [info] awsCfnLsp: Candidate versions: 1.1.0[darwin-arm64,darwin-x64,linux-arm64,linux-x64,win32-arm64,win32-x64,windows-arm64,windows-x64], 1.0.0[darwin-arm64,darwin-x64,linux-arm64,linux-x64,win32-arm64,win32-x64,windows-arm64,windows-x64]
2025-11-24 17:58:11.078 [info] awsCfnLsp: Creating CloudFormation LSP manifest for prod
2025-11-24 17:58:12.270 [info] lsp: Finished preparing "cloudformation-languageserver" LSP server: '/Users/tennakoo/Library/Caches/aws/toolkits/language-servers/cloudformation-languageserver/1.1.0'
2025-11-24 17:58:12.312 [info] awsCfnLsp: Found CloudFormation LSP executable: /Users/tennakoo/Library/Caches/aws/toolkits/language-servers/cloudformation-languageserver/1.1.0/cloudformation-languageserver-1.1.0-darwin-arm64-node22/cfn-lsp-server-standalone.js
```

*No tests added since no business logic modified*

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Akila Tennakoon <[email protected]>

## Problem
- Project node is not loading automatically after re-authentication

## Solution
- After re-authentication, set the project, then refresh the node

## User experience
- the user will see select project popup after re-authentication 

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Co-authored-by: Build User <[email protected]>

… catalog (#8363)

## Problem
A bug is reported that when s3 table catalog is empty, there is
getDatabases call being made and cause unwanted error

## Solution
Handle the issue by not calling getDatabases when a catalog node is an
empty parent node



---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Zulin Liu <[email protected]>

…re remote connections (#8328)

## Problem
When attempting to connect to a SageMaker Space, if the user's SSH
config has syntax errors (even outside the sm_* section), users would
see a cryptic error message:

```ssh check against host failed: 255```

This error message:
Didn't explain what was wrong
Didn't indicate it was an SSH config issue
Didn't provide a way to fix the problem

## Solution
Enhanced the SSH configuration error handling to provide a better user experience:

Shows a clear message explaining the issue.
Displays the actual SSH error (including line numbers) 
Provides an "Open SSH Config" button to directly open the config file for editing


https://github.com/user-attachments/assets/ef4f5a0f-0525-4e4c-9e96-a2081997dd81



---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

…rget old linux builds (#8383)

## Problem
* Fix potential GitHub API rate limiting issue
* Use older build of linux for older machines

## Solution
* Attempt using manifest json to resolve cfn lsp versions, fallback to
original GitHub releases approach
* When in a sandbox environment, or required version of GLIC is not
available, use older version of linux build

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

#8338)

…EATE_COMPLETE and add delete button for CREATE_FAILED change sets

## Problem
- The "Deploy Changes" button is present when viewing a change set even
if the change set does not have CREATE_COMPLETE status
- Additionally, the "Delete Changeset" button is not present when no
changes are detected in the change set

## Solution
- Added logic to check if the change set has CREATE_COMPLETE status
before enabling the deploy changes button
- Added the "Delete Changeset" button for the view when no changes are
detected
- Additionally, upon pressing the "Delete Changeset" button on the "no
changes are detected" view, the button disappears to prevent additional
delete attempts

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
- Allow for the ability to configure cfn-lint. Minimal impact to the
settings panel by using a nest object

## 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

#8367)

…g for deployment mode first

## Problem
When customer wants to validate/deploy in REVERT_DRIFT mode, they have
to answer pre-requisite prompts correctly before they get prompted for
deployment mode.

## Solution
Ask for deployment mode first and don't ask the other prompts with
incompatible answers.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Akila Tennakoon <[email protected]>

#8398)

[fix(cloudformation): Only remap legacy linux builds, if they are
available](b5a2c7f)

## 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Description
- Added existing E2E tests to PR runners for `MacOS`, `Ubuntu` and
`Windows`
- Configured LSP server to be pre downloaded before the tests starts
using the manifest and added a fallback to download directly from Github
releases
- Printing extension logs in the test runners if there are test failures
---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Deep Furiya <[email protected]>

## Problem


## Solution
replacing previous check with LMI checks for `CapacityProviderConfig`

## Notice: Lambda SDK version 3.731 doesn't have this field yet. And
updating the SDK causes a lot of compatible issue.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
We removed the test in
:https://github.com/aws/aws-toolkit-vscode/pull/8318/files
due to localproxy not mocked correctly.
## Solution
Fixed the issue and now adding back these tests.
This test starts a mock server and captures the actual user-agent being
sent to make sure we are sending correct UA.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

## Problem
LMI function contains new property and we have new CapacityProvider
property

## Solution

- Add support for `AWS::Serverless::CapacityProvider` resource type in
explorer
- Display capacity provider properties in resource nodes
- Stringify CloudFormation intrinsic functions in property nodes for
better readability
- Add type-safe resource entity interfaces (FunctionResourceEntity,
CapacityProviderResourceEntity)
- Add type guards (isFunctionResource, isCapacityProviderResource) for
safer resource handling
- Hide property node if not defined
- Fix optional chaining for Architectures array access to prevent
undefined errors
- Add test coverage for capacity provider resources with intrinsic
functions

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: chungjac <[email protected]>

**Description**
Updating the IAM domain check to use the IamSignIns attribute instead of
using Domain preferences.

**Testing Done**
Tested locally.

---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Bhargava Varadharajan <[email protected]>

This merges the released changes for rc-20251209 into main.
MCM-140109917

---------

Co-authored-by: aws-toolkit-automation <>

…#8396)

## Summary

This PR migrates the GlueCatalog custom API client from the deprecated
AWS SDK v2 generator pattern to standalone AWS SDK v3-compatible
packages. This migration is required as part of the broader AWS Toolkit
repository migration from SDK v2 to v3.

The AWS Toolkit VSCode repository is deprecating the centralized
generateServiceClient.ts script that generates TypeScript clients from
service JSON definitions. The SageMaker Unified Studio (SMUS) team
currently uses this v2 generator for GlueCatalog.

## Solution
* Created standalone package @amzn/glue-catalog-client
* Updated imports to use new standalone package
* Removed dependency for `GlueCatalogApi` on the deprecated
generateServiceClient.ts script
---

- 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.