-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update pyenv GitHub Action #428
base: main
Are you sure you want to change the base?
Update pyenv GitHub Action #428
Conversation
…on v3.9.11 Sent PR to the upstream maintainer
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.
Please use the latest gabriel falcao release
Why can't you just do it? Aren't you the maintainer with the broken build? It's silly that you are all comfortable utilizing a repository from some random dude that you've never met off his personal GitHub account versus mine but yeah let's keep it "professional" and "official" even though he just merged my PR and the code is literally identical. BTW I'm in touch with the the maintainer and we are moving this action onto an organization so I can just maintain it no PRs required. Won't that make your life easier? |
Done. |
.github/workflows/installation.yaml
Outdated
@@ -23,7 +23,7 @@ jobs: | |||
path: /opt/hostedtoolcache/pyenv_root | |||
key: ${{ runner.os }}-pyenv | |||
- name: Install pyenv versions | |||
uses: blakewatters/pyenv-action@v9 | |||
uses: gabrielfalcao/pyenv-action@v9 |
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.
Done. Thanks for the support. |
Switched the pyenv-action over to a forked version that can install Python v3.9.11. PR sent upstream but no idea how responsive the maintainer is