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

Revert "chore(deps): bump gradle/actions from 3 to 321 (#1572)" #1579

Merged
merged 1 commit into from
Apr 9, 2024

Conversation

chaoran-chen
Copy link
Member

@chaoran-chen chaoran-chen commented Apr 9, 2024

This reverts #1572.

The checks in #1572 passed (maybe due to caches? I didn't check) but gradle/actions@v321 doesn't actually seem to exist. Sorry for merging!

This reverts commit 390c565.

gradle/actions@v321 doesn't actually seem to exist.
@chaoran-chen chaoran-chen merged commit d7c4f10 into main Apr 9, 2024
11 checks passed
@chaoran-chen chaoran-chen deleted the fix-gradle-actions branch April 9, 2024 12:25
@corneliusroemer
Copy link
Contributor

corneliusroemer commented Apr 9, 2024

I looked into it: CI passed because v321 actually existed as a tag. But the devs must have revoked it as it was missing the dots in error.

https://github.com/loculus-project/loculus/actions/runs/8605209435/job/23580981080

image

I think the lesson is to check whether the version contains an obvious error: a jump from 3 to 321 makes no sense under semantic versioning - but I don't think this will happen frequently.

See gradle/actions#130

@chaoran-chen
Copy link
Member Author

Ah, interesting. They have version 3.2.1 and I assumed that they decided to encode it as 321.

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

Successfully merging this pull request may close these issues.

4 participants