Amazon Q and AWS Toolkit are now published to Open VSX: https://open-vsx.org/namespace/amazonwebservices

from aws-toolkit-vscode.

Actually toolkit failed in the past few days/week until 3.2.0 was tagged as latest yesterday.

from aws-toolkit-vscode.

Thanks for raising this.

The publishing workflow used to work (#1355) but now it's breaking as you're releasing both AmazonWebServices.amazon-q-vscode and AmazonWebServices.aws-toolkit-vscode in the same repo.

That's unfortunate. We publish each vsix artifact to different tags, e.g.:

• https://github.com/aws/aws-toolkit-vscode/releases/tag/amazonq%2Fv1.2.0
• https://github.com/aws/aws-toolkit-vscode/releases/tag/toolkit%2Fv3.2.0

does that help?

from aws-toolkit-vscode.

The current pull workflow apparently fetches vsix file from latest tag only. Instead of patching the pull workflow, I think the ultimate fix is to push to Open VSX from here. There are AWS services such as the code editor in SageMaker Studio using this extension on Open VSX.

from aws-toolkit-vscode.

Oh, I misunderstood something: it looks like AWS Toolkit is still being pulled: https://open-vsx.org/extension/amazonwebservices/aws-toolkit-vscode/changes

So this doesn't necessarily "break" anything, but we do need to think about how to publish Amazon Q.

from aws-toolkit-vscode.

Workaround

As a workaround, you can install the Amazon Q extension directly from our published downloads. The vsix file(s) provided there are identical to what we would publish to OpenVSX.

How to install

1. Download Amazon Q (amazon-q-vscode*.vsix) or AWS Toolkit (aws-toolkit-vscode*.vsix) from https://github.com/aws/aws-toolkit-vscode/releases
2. Run Extensions: Install from VSIX... from the VSCode command palette and choose the vsix file(s).

from aws-toolkit-vscode.