Skip to content
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

How to get older releases of this extension #155

Open
InsidiousForce opened this issue May 3, 2021 · 3 comments
Open

How to get older releases of this extension #155

InsidiousForce opened this issue May 3, 2021 · 3 comments

Comments

@InsidiousForce
Copy link

I have an issue with the new extension crashing when publishing to lambda. Even tried a brand new project. So maybe something with my machine. I was going to roll back to a previous extension, but the marketplace has no extension history. Is there an archive of older versions? I updated from 1.18.1.0 to 1.12.1.0 and want to go back. Unlike the extensions for vscode, there is no source and no releases.

Vscode: https://github.com/aws/aws-toolkit-vscode/releases

Vs: no source repo, no previous releases

@awschristou
Copy link
Contributor

Hi @LilMinmax can you please check your log files within %localappdata%\AWSToolkit\logs\visualstudio for some clues you can share around your issue? It's preferable to continuously stay on newer extension versions for bug fixes and newer functionality.

@InsidiousForce
Copy link
Author

I figured out the issue, but it set me back a few hours that I needed to not be set back. I shouldn't have upgraded during a time where I'd be stressed if something broke, but that seems to be a lot lately and in this case I wanted to move a lambda to .net5 for reasons, and needed the docker image support. In this case I could have reverted to a previous version and kept working.

Will this end up a project like the VSCode extension with source and release history?

Feel free to close this after your reply. Appreciate it.

@awschristou
Copy link
Contributor

Thanks for the update @LilMinmax - was the issue something caused by the Toolkit that we could investigate?

Will this end up a project like the VSCode extension with source and release history?

This is on the roadmap!

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

No branches or pull requests

2 participants