chore(v4): Remove amazon-q-vscode from SMUS Code Editor#1255
Open
marfriaz wants to merge 1 commit into
Open
Conversation
Remove the Amazon Q extension (amazon-q-vscode) from the SMUS (sagemaker-ui) Code Editor extension list as part of the SMUS Amazon Q deprecation. Kept aws-toolkit-vscode (AWS Toolkit, not Q). Scope: SMUS only -- this does NOT affect SageMaker AI (SMAI). This edits extensions-sagemaker-ui.txt, which installs into the separate sagemaker-ui-code-editor-server-data dir used by the SMUS Code Editor. The standalone SMAI Code Editor installs from extensions.txt (sagemaker-code-editor-server-data), which is unchanged and still includes amazon-q-vscode. Lands in the next 4.x minor build (4.3+); released 4.0-4.2 patch lines are unaffected (SemVer: patch releases do not add or remove packages).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Remove the Amazon Q extension (
amazon-q-vscode) from the SMUS (sagemaker-ui) Code Editor extension list as part of the SMUS Amazon Q deprecation.aws-toolkit-vscode(AWS Toolkit, not Q) is kept.Scope: SMUS only — this does NOT affect SageMaker AI (SMAI). This edits
extensions-sagemaker-ui.txt, which installs into the separatesagemaker-ui-code-editor-server-datadir used by the SMUS Code Editor. The standalone SMAI Code Editor installs fromextensions.txt(sagemaker-code-editor-server-data), which is unchanged and still includesamazon-q-vscode.Lands in the next 4.x minor build (4.3+); released 4.0–4.2 patch lines are unaffected (SemVer: patch releases do not add or remove packages).
Type of Change
Release Information
Does this change need to be included in patch version releases? By default, any pull requests will only be added to the next SMD image minor version release once they are merged in template folder. Only critical bug fix or security update should be applied to new patch versions of existed image minor versions.
If yes, please explain why:
N/A — this is an intentional package removal and must ship as a new minor (4.3+), not a patch. Per the SMD support policy, patch releases do not add or remove packages; removing the VSIX from an existing minor would be a backwards-incompatible change.
How Has This Been Tested?
Validated by building the v4 image and launching Code Editor:
sagemaker-ui-code-editor-server-data):amazon-q-vscodeis no longer installed;aws-toolkit-vscode, Python, and Jupyter extensions remain.sagemaker-code-editor-server-data): unaffected —amazon-q-vscodestill present (installed fromextensions.txt).Checklist:
Test Screenshots (if applicable):
N/A
Related Issues
N/A (SMUS-internal Amazon Q deprecation tracking)
Additional Notes
Single-line change to
template/v4/dirs/etc/code-editor/extensions-sagemaker-ui.txt(one deletion). No build-tool, settings, or documentation changes. The two extension lists install into separate server-data directories, which is what scopes this to SMUS without touching SMAI.