[DOCU-2735] DOC: Automate module version updates after release Created: 01/Jun/23  Updated: 13/Jun/23  Resolved: 13/Jun/23

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

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

Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCU-2736 DOC: Add all git links Sub-task Closed Adrian Brooks  
DOCU-2737 DOC: Add bash commands to automatical... Sub-task Closed Adrian Brooks  
DOCU-2738 DOC: Test locally on the 6.2.35 relea... Sub-task Closed Adrian Brooks  
DOCU-2740 DOC: Code clean up and modularisation Sub-task Closed Adrian Brooks  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Continue to iterate on the module_versions_checks script described here.

Next steps

  1. Add all git links, so that the script injects new version numbers for all changed modules (currently only the first 11 modules) --> Review again with Alex & Martin
  2. Add bash commands to automatically create a PR with the changes already injected into a local playbook by the script --> Review again with Alex & Martin
  3. Code clean up and modularisation (e.g., so that we can switch to git commands easily instead of scraping with selenium if we want)
  4. Test locally on the 6.2.35 release for the audit use case

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