-
Notifications
You must be signed in to change notification settings - Fork 2
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
Retime JS dependency update cron, and make new dependabot alert issue #239
Labels
Comments
GuySartorelli
changed the title
Retime JS dependency update cron
Retime JS dependency update cron, and make new dependabot alert issue
May 6, 2024
This was referenced May 29, 2024
We can configure the branch dependabot uses - but it's a bit confusing. It looks like it'll still use the default branch for dependabot alerts but then create pull requests against the branches you define? I'd rather not mess with this. It's more consistent to get alerts and PRs for the same branch. |
Reassigning to Guy to:
|
Both actions work well. |
PRs merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a recent CMS Squad retrospective we identified that the cron for creating the "JS pull-requests" GitHub issue is out-of-sync with our release schedule.
Currently this issue is created quarterly, with the second one being created shortly after a minor release. We do a minor release every 6 months.
Acceptance criteria
js-prs-issue.yml
to run every 6 months, roughly 1 month before we'd schedule a beta releaseupdate-js
workflows for all supported modules to run every 6 months, roughly 1 month before we'd schedule a beta releasePRs
Module Standardiser PRs
The text was updated successfully, but these errors were encountered: