Create common renovate config that automates @edx namespaced minor/patch version upgrades

[adamstankiewicz]

Across many frontend repos in Open edX, Renovate is used to automated node_modules dependency upgrades according to semver ranges (if applicable) defined for packages in package.json.

All of the Open edX NPM packages are prefixed with @edx and all (should) adhere to semantic versioning in that a new major version will be published (e.g., v1 -> v2) if a release is a breaking change for consumers.

Because of this, we could help product teams with updates to any NPM packages that are within the @edx namespace, for example @edx/paragon, @edx/frontend-platform, @edx/frontend-build, etc.

By doing so, product teams could automatically get bug fixes and new features upgraded and merged for @edx packages, and only have to manually intervene for breaking changes (new major versions).

This could likely be implemented by creating a custom Renovate preset that each repository's renovate.json file could optionally extends. The preset could

Alternatively, a script could probably be written to modify read/update renovate.json files in a collection of checked out repositories.

Example Renovate config to automerge @edx namespaced NPM packages for patch/minor upgrades:

{
  "packageRules": [
    {
      "matchPackagePatterns": ["^@edx/"],
      "matchUpdateTypes": ["minor", "patch"],
      "automerge": true
    }
  ]
}

If this were implemented as a custom Renovate preset, it might be worth checking if it's possible to provide an optional exclusion list so consumers of the preset can opt-out of auto-merging specific @edx namespaced package upgrades.

CI must pass before the upgrade is merged.

[abdullahwaheed]

@adamstankiewicz should i schedule these configurations or use default or previous configurations?

[abdullahwaheed]

Repos Checklist:

• https://github.com/openedx/frontend-app-publisher
• https://github.com/openedx/frontend-app-gradebook
• https://github.com/openedx/frontend-app-admin-portal
• https://github.com/openedx/frontend-app-profile
• https://github.com/openedx/frontend-app-ecommerce
• https://github.com/openedx/frontend-app-account
• https://github.com/openedx/frontend-app-payment
• https://github.com/openedx/frontend-app-learner-portal-programs
• https://github.com/openedx/frontend-app-learning
• https://github.com/edx/prospectus
• https://github.com/openedx/frontend-app-program-console
• https://github.com/openedx/frontend-app-learner-portal-enterprise
• https://github.com/openedx/studio-frontend
• https://github.com/openedx/frontend-app-course-authoring
• https://github.com/openedx/frontend-app-library-authoring
• https://github.com/openedx/frontend-app-programs-dashboard
• https://github.com/edx/frontend-app-learner-record
• https://github.com/openedx/frontend-app-enterprise-public-catalog
• https://github.com/edx/frontend-app-communications
• https://github.com/openedx/paragon
• https://github.com/openedx/frontend-platform
• https://github.com/openedx/frontend-build
• https://github.com/openedx/frontend-component-header
• https://github.com/edx/frontend-component-header-edx
• https://github.com/openedx/frontend-component-cookie-policy-banner
• https://github.com/edx/frontend-component-footer-edx
• https://github.com/openedx/frontend-component-footer
• https://github.com/openedx/frontend-enterprise
• https://github.com/openedx/eslint-config
• https://github.com/openedx/stylelint-config-edx
• https://github.com/openedx/frontend-template-application

[feanil]

FYI, I got the last couple of PRs that were outstanding here merged so now all PRs listed here are merged. @abdullahwaheed I don't know if this issue can now be closed or if you have other outstanding work?

[abdullahwaheed]

yes, i think we can close it now