-
Notifications
You must be signed in to change notification settings - Fork 13
chore: create Issue when Angular bump fails #121
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
chore: create Issue when Angular bump fails #121
Conversation
Configure Renovate to create PRs bumping Angular packages in test fixtures, and add a CI workflow to automatically create an Issue when one of these PRs fails. Separately, we'll configure an integration from GitHub Issues to our triage inbox. This allows us to find out proactively when new or upcoming releases may cause regressions, before users are affected. See netlify/remix-compute#355 and netlify/remix-compute#365.
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
packageNames: [ | ||
// Those cannot be upgraded to requiring ES modules | ||
'strip-ansi', | ||
], | ||
major: { | ||
enabled: false, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whatever this was, it's already in our shared config
dependencyDashboard: true, | ||
automerge: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are already set upstream
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Configure Renovate to create PRs bumping Angular packages in test fixtures, and add a CI workflow to automatically create an Issue when one of these PRs fails. Separately, we'll configure an integration from GitHub Issues to our triage inbox.
This allows us to find out proactively when new or upcoming releases may cause regressions, before users are affected.
See netlify/remix-compute#355 and netlify/remix-compute#365.