[MGNLFE-506] System to ensure we keep FE-helpers up to date Created: 15/Jun/23  Updated: 28/Aug/23  Resolved: 28/Aug/23

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Robert Šiška
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 1h Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLFE-507 Implementation Sub-task Completed Robert Šiška  
MGNLFE-508 Review Sub-task Completed Milan Divilek  
MGNLFE-509 Pre-Integration QA Sub-task Completed Milan Divilek  
MGNLFE-510 QA Sub-task Closed Oanh Thai Hoang  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: SPA On The Ball
Sprint: DevX 44, DevX 45
Story Points: 2
Team: DeveloperX
Work Started:

 Description   

See where this ticket is tagged here: Pro-actively update frontend-helpers at least once a month.

Use cases:

As an customer I want Magnolia FE libraries to be using/compatible with  recent versions of the frontend frameworks like React, Angular, Vue. That do not use libraries with vulnerabilities.

As a Magnolia developer, I want to have a process or system that ensures that all libraries and demos are up to date so that I am not embarrassed when a customer points it out. For example notifications, reminders, auto ticket creation, auto pull request creation etc.

Note:

We should devise this plan with Services team. They will have good input and may have some responsibilities for the demos as well.

 



 Comments   
Comment by Robert Šiška [ 09/Aug/23 ]

We are already using renovate bot. It can be configured to keep the "LTS" versions of specific libraries:

{    "matchPackageNames": ["react", "react-dom", "react-test-renderer"],    "groupName": "react monorepo",    "matchUpdateTypes": ["minor", "patch"] }

,

{    "matchPackagePatterns": ["@angular/.*", "@angular-devkit/.*", "@angular-eslint/.*", "@angular-builders/.*"],    "groupName": "angular monorepo",    "allowedVersions": "<15" }

These versions will have to be adjusted manually, when we update the libraries to newer version framework.

For the demo projects (like e.g. minimal-headless-spa-demos), the default renovate configuration can be used. See the current renovate.json file.

Generated at Mon Feb 12 05:48:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.