build: remove repo.spring.io from workflows#7340
Merged
jeremylong merged 1 commit intodependency-check:mainfrom Jan 22, 2025
Merged
build: remove repo.spring.io from workflows#7340jeremylong merged 1 commit intodependency-check:mainfrom
jeremylong merged 1 commit intodependency-check:mainfrom
Conversation
The FP workflows are failing due to this repo being unauthorised for access. Not sure how it was working before unless there was an authentication token somewhere, as anonymous access I believe was blocked some time ago. Do we need this here, or is Maven Central good enough?
Collaborator
|
The repo is unnecessary - I think I was trying to add as many alternatives as possible in case the FP came from another public repo. If this is no longer public we should remove it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The FP workflows are failing due to this repo being unauthorised for access. Not sure how it was working before unless there was an (expired?) authentication token somewhere, as anonymous access I believe was blocked some time ago.
Do we need this here, or is Maven Central good enough?