Skip to content

chore(v4): Remove amazon-q-vscode from SMUS Code Editor#1255

Open
marfriaz wants to merge 1 commit into
aws:mainfrom
marfriaz:marfriaz/remove-q-vscode-code-editor-v4
Open

chore(v4): Remove amazon-q-vscode from SMUS Code Editor#1255
marfriaz wants to merge 1 commit into
aws:mainfrom
marfriaz:marfriaz/remove-q-vscode-code-editor-v4

Conversation

@marfriaz

@marfriaz marfriaz commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

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 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).

Type of Change

  • Image update - Bug fix
  • Image update - New feature
  • Image update - Breaking change
  • SMD image build tool update
  • Documentation update

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.

  • Yes (Critical bug fix or security update)
  • No (New feature or non-critical change)
  • N/A (Not an image update)

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:

  • SMUS Code Editor (sagemaker-ui-code-editor-server-data): amazon-q-vscode is no longer installed; aws-toolkit-vscode, Python, and Jupyter extensions remain.
  • Standalone SMAI Code Editor (sagemaker-code-editor-server-data): unaffected — amazon-q-vscode still present (installed from extensions.txt).

Checklist:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works

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.

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).
@marfriaz marfriaz requested a review from a team as a code owner July 7, 2026 18:45
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.

2 participants