8000 ci: only publish amazonq as "latest" release by justinmk3 · Pull Request #7408 · aws/aws-toolkit-vscode · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ci: only publish amazonq as "latest" release #7408

8000
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 30, 2025

Conversation

justinmk3
Copy link
Contributor

Problem:
The browser_download_url in https://api.github.com/repos/aws/aws-toolkit-vscode/releases/latest points to a random artifact depending on whether toolkit or amazonq was the last release to publish.

Solution:
Modify the deploy logic to only set "latest" for "amazonq", never "toolkit".


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

Problem:

The `browser_download_url` in https://api.github.com/repos/aws/aws-toolkit-vscode/releases/latest
points to a random artifact depending on whether toolkit or amazonq was
the last release to publish.

Solution:
Modify the deploy logic to only set "latest" for "amazonq", never
"toolkit".
@justinmk3 justinmk3 requested a review from a team as a code owner May 30, 2025 18:22
@justinmk3 justinmk3 merged commit d41e749 into aws:master May 30, 2025
15 of 22 checks passed
@justinmk3 justinmk3 deleted the fixrelease branch May 30, 2025 18:29
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.

3 participants
0