Upgrade undertow, report dependencies to GitHub #944
Merged
Conversation
This file contains 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
Undertow < 2.2.30.Final has multiple security alerts (e.g. https://github.com/zio/zio-streams-compress/security/dependabot/14). This upgrades Undertow to the fixed version. Also add a workflow for reporting the dependencies to GitHub, allowing security warnings from GitHub.
|
@tgodzik Thanks for merging. Please don't forget to enable the |
|
Ach, forgot it needed to be enabled, separately, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Undertow < 2.2.30.Final has multiple security alerts (e.g. https://github.com/zio/zio-streams-compress/security/dependabot/14). This upgrades Undertow to the fixed version.
Also add a workflow for reporting the dependencies to GitHub, allowing security warnings from GitHub.
As described on https://github.com/marketplace/actions/sbt-dependency-submission, before running the workflow, make sure that the
Dependency Graphfeature is enabled in the settings of your repository (Settings>Code Security and Analysis).The graph of your sbt build will be visible in the Dependency Graph page of the
Insightstab.