-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use silverstripe/supported-modules #3
Comments
There's a Note that we will need to add a |
We should keep things silverstripe/cwp-search where there was a CMS 5 unsupported version released in the CMS 4 builds but exclude them from the CMS 5 builds |
PR merged. |
PR merged. Reassigning to Steve to deploy |
New PR merged. Reassigned to Steve for deployment. |
Have tested builds + merge-up jobs on UAT, all working. Have deployed to prod. Closing |
Currently rhino runs off a hardcoded list for the modules it pulls information for
This isn't great because it includes some unsupported modules in the builds list and we waste time remedying them
It should instead use silverstripe/supported-modules
Note that- That's no longer relevant as of #17silverstripe/supported-modules
doesn't list some repositories we care about such as the gha* repositories. Either they should be added to the supported-modules JSON, or we need to keep them hardcoded here.Acceptance criteria
silverstripe/supported-modules
repocomposer update silverstripe/supported-modules
in rhino and redeploy it.PRs
Post merge supported-modules PR
The text was updated successfully, but these errors were encountered: