Skip to content
This repository has been archived by the owner on Feb 9, 2021. It is now read-only.

Only add ruby in $PATH, do not overwrite /usr/bin/ruby #29

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

eregon
Copy link
Contributor

@eregon eregon commented Sep 21, 2019

  • Fixes UnhandledPromiseRejectionWarning on macOS #18
  • The symlink never worked on macOS, and there was a missing await.
  • No tool should hardcode /usr/bin/ruby, but instead executables
    should use #!/usr/bin/env ruby.
  • If a specific tool needs the symlink, then it can of course be
    added as part of the steps of that CI.

* Fixes actions#18
* The symlink never worked on macOS, and there was a missing `await`.
* No tool should hardcode `/usr/bin/ruby`, but instead executables
  should use `#!/usr/bin/env ruby`.
* If a specific tool needs the symlink, then it can of course be
  added as part of the steps of that CI.
@tlvenn
Copy link

tlvenn commented Oct 5, 2019

Hi @eregon, any chance to get this merged soon ? Thanks in advance !

@eregon
Copy link
Contributor Author

eregon commented Oct 5, 2019

@damccorm Could you review this?

@CAMOBAP
Copy link

CAMOBAP commented Nov 12, 2019

@bryanmacfarlane may we kindly ask you to have a look at this in near time 🙏

@bryanmacfarlane
Copy link
Member

👀

@dentuzhik
Copy link

We have eventually ended up forking setup-ruby with this patch merged and have been using this with no issues for a couple of months. It would be great to migrate back to upstream though :)

@eileencodes eileencodes merged commit 9562cfc into actions:master Jan 9, 2020
@dentuzhik
Copy link

Nice!
Hopefully we can expect a new tag some time soon :)

@eregon eregon deleted the no-symlink-usr-bin branch January 10, 2020 11:28
@dentuzhik
Copy link

@eileencodes sorry for a direct ping, but is it possible to have this tagged through git, so we don't have to reference unstable master? It has been a week since this PR got merged, and we would really like to drop our fork.

Or do you plan to bundle more changes into the next version, whatever that would be?

@bryanmacfarlane
Copy link
Member

I can handle that hopefully today.

@dentuzhik
Copy link

Much appreciated 🙇

@bryanmacfarlane
Copy link
Member

@dentuzhik , I created a v1.1.1 release and tag. Can you validate it using @v1.1.1 and if you give the green light, I'll push v1 tag

@dentuzhik
Copy link

👍 we will let you know asap, thanks a lot!

@dentuzhik
Copy link

Everything seems working fine for us, though we are wondering why do you want to override existing v1 tag, rather than create a new one (v1.1 or v2).

There have been quite a few things merged lately, and I have no context whether it's ok for everyone else using v1 atm

@bryanmacfarlane
Copy link
Member

bryanmacfarlane commented Jan 17, 2020

Because folks that bind to v1 are asking for the latest released version 1 major version. v1 is logically equivalent to 1.x. If a user doesn't want latest, they would bind to the exact release version or the sha.

https://github.com/actions/toolkit/blob/master/docs/action-versioning.md

Actions are major versioned when there are compat or behavior breaks.

Note there are no minor tags published. Just exact versions and major tag.

@eregon
Copy link
Contributor Author

eregon commented Apr 25, 2020

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UnhandledPromiseRejectionWarning on macOS
6 participants