-
Notifications
You must be signed in to change notification settings - Fork 5
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
fix error on picking latest vault releases #56
Conversation
Hi @markmartirosian! Thanks a lot for catching this bug and raising this PR! I've created some test cases for |
@dbanck something like this? (; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the PR with the changes from main
and providing a test case!
Can you explain what your motivation is behind extending your solution? I think the one-line filter was an elegant solution as a bug fix.
Do you mind removing the changes to package-lock.json
? Unfortunately, this project still uses an older version of npm, so the lock file is still version 1. I'm planning to update this in a separate PR soon.
@dbanck both codepaths: 1. I've copied You should have write permissions to the fork repo. |
Thanks for the write access! I rebased from Unifying the versions for both code paths makes sense! I've added a new type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for reporting and fixing this bug! 👍
The version
1.2.6.1+ent
is not valid semver in https://releases.hashicorp.com/vault/index.json.