This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
fix: Bump scala rules to a version using secure maven central #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of Jan 15th central is requiring secure connections. https://central.sonatype.org/articles/2019/Apr/30/http-access-to-repo1mavenorg-and-repomavenapacheorg-is-being-deprecated/
The errors I've seen are similar to this, that relates to the annocement:
Current scala dependency version we've pinned is using insecure connection, so it needs to be bumped e.g. to run
sync-deps
andformat
. PR discussing this issue and PR's resolving it: bazelbuild/rules_scala#920