Override postgresql version defined by spring-boot-dependencies #1416
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.
🎫 Ticket
https://jira.cms.gov/browse/AB2D-6397
🛠 Changes
postgres.version
topostgresql.version
to properly override version defined inspring-boot-dependencies
.ℹ️ Context
The postgres version defined by
spring-boot-dependencies
is 42.3.8. Snyk flags this version as vulnerable.Modules common and job override this version to 42.7.3. However, when another module imports one of these modules, Maven does not select this overridden version and instead selects the version defined by
spring-boot-dependencies
.🧪 Validation
Running
mvn dependency:tree
on main shows different versions being used for different modules.On the feature branch, the same version is used across all modules.