Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCU-2735

DOC: Automate module version updates after release

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • None

    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

      Checklists

        Acceptance criteria

        Attachments

          There are no Sub-Tasks for this issue.

          Activity

            People

              abrooks Adrian Brooks
              abrooks Adrian Brooks
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR