[MGNLCE-76] Automate validation that the bundle pom depends on the latest magnolia module versions (when not in CL) Created: 13/Mar/17  Updated: 02/Jun/22  Resolved: 02/Jun/22

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Michael Mühlebach Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: artt, foundation_team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-753 Make sure that latest versions of int... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Release automation

 Description   

It can happen, that new versions of modules are forgotten to be updated in the bundle pom. An easy way to validate this is to check if there are new versions with the maven versions plugin. For the records, an equivalent check is being done for ParentPomLatestVersionPreflightCheck.

Acceptance Criteria

  • On release branches only maintenance releases should be considered

Generated at Mon Feb 12 00:06:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.