Skip problematic dependency update
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
Yes. The Frogbot dependecy pr will not finishe. It fails because could not update.
[Error] the following errors occured while fixing vulnerabilities in /tmp/jfrog.cli.temp.-1715065723-4003941656:
couldn't update "org.springframework.ws:spring-ws" to suggested fix version: Version 2.4.4 is not available for artifact
##[error]Bash exited with code '1'.
Describe the solution you'd like to see
I would like to have parameter, to define, that Frogbot will skip the problematic dependency update.
Describe alternatives you've considered
non
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating Frogbot's dependency-update configuration and the handling of unavailable suggested versions; done means a parameter can exclude a problematic update without failing the dependency-update process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, spring
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100