-
Notifications
You must be signed in to change notification settings - Fork 70
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
Bump to latest setup-gel action #1230
base: master
Are you sure you want to change the base?
Conversation
Use the `gel` CLI instead of `edgedb`
@@ -63,20 +63,20 @@ jobs: | |||
yarn format | |||
|
|||
- name: Install Gel | |||
uses: geldata/setup-gel@6763b6de72782d9c2e5ecc1095986a1c707da68f | |||
uses: geldata/setup-gel@358410cc5618fa956d16f1b7157a8c86f9b517cf # v1.4 |
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.
This is our trusted action, so just using v1
is fine.
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.
Well, I mostly mean this to be stable across runs rather than a lack of trust of the upstream. But I'm not sure what we actually get from that, so fair enough!
We were accidentally fire-and-forgetting this promise rather than awaiting it and letting it reject the outer promise. Will be introducing more strict linting rules to catch cases like this soon.
No description provided.