[BUILD-753] Make sure that latest versions of internal modules are used (even when not in CL) Created: 20/Apr/22  Updated: 19/Dec/22  Resolved: 21/Nov/22

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-978 Roll out a Magnolia-specific Renovate... Closed
is related to MGNLCE-76 Automate validation that the bundle p... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Release automation
Team: Foundation
Work Started:

 Description   

Note: this is true exclusively of bundles.

In the 6.2.18 release lang 1.1.10 was the latest available version but was not updated in CE pom by any developer and wasn't present in the CL. Hence, the 1.1.9 version was released.

A preflight check could make sure that internal dependencies are at their latest available releases.

Maven version plugin could possibly be used to that purpose, e.g. for properties

mvn versions:update-properties -DallowIncrementalUpdates=true -DallowMajorUpdates=false -DallowMinorUpdates=false

and for dependencies 

mvn versions:use-releases

Even easier: let's configure Renovate to access Nexus so it can see where we fall behind with our own artifacts.


Generated at Sun Feb 11 23:44:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.