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

.github/,go.mod,go.sum: Update storj dependencies, drop older go versions #468

Merged
merged 7 commits into from
Apr 19, 2022

Conversation

stefanbenten
Copy link
Collaborator

@stefanbenten stefanbenten commented Feb 17, 2022

  • Bumps storj dep to v1.8.2
  • Drops go v1.13 and go v1.14 since they are outdated and not supported by some recent dependencies
  • Bumps go version for testing to latest stable release v1.18

@stefanbenten stefanbenten added the reviewer-can-merge This Pull Request is fine to merge after approval. label Feb 17, 2022
@aspacca
Copy link
Collaborator

aspacca commented Feb 17, 2022

@stefanbenten can you look at 1.13 and 1.14 failure? we could also remove them in case

@stefanbenten
Copy link
Collaborator Author

I'll look into it. Seems like an unwanted dependency bump in the uplink package.

@stefanbenten stefanbenten changed the title go.mod,go.sum: Update storj dependencies go.mod,go.sum: Update storj dependencies, drop older go versions Apr 3, 2022
@stefanbenten stefanbenten changed the title go.mod,go.sum: Update storj dependencies, drop older go versions .github/,go.mod,go.sum: Update storj dependencies, drop older go versions Apr 3, 2022
@stefanbenten
Copy link
Collaborator Author

@aspacca Since Go v1.18 is now released (and soon available for github actions), i dropped older v1.13 and v1.14 and prepared the workflows to use the latest version.

@stefanbenten
Copy link
Collaborator Author

stefanbenten commented Apr 10, 2022

@aspacca This should be good to go now.

We need to drop the required build status for v1.13/4 and require v1.17/8 to pass.

@aspacca aspacca merged commit eeff2c8 into main Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reviewer-can-merge This Pull Request is fine to merge after approval.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants