-
Notifications
You must be signed in to change notification settings - Fork 10
chore(renovate): configure @remix-run bumps in test fixtures #355
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
Merged
serhalp
merged 1 commit into
main
from
serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause
May 24, 2024
Merged
chore(renovate): configure @remix-run bumps in test fixtures #355
serhalp
merged 1 commit into
main
from
serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause
May 24, 2024
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for remix-edge ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for remix-serverless ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
023a84f
to
23c5e88
Compare
mrstork
reviewed
May 24, 2024
23c5e88
to
43264f0
Compare
43264f0
to
655170e
Compare
mrstork
approved these changes
May 24, 2024
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.
LGTM
serhalp
added a commit
to netlify/angular-runtime
that referenced
this pull request
May 28, 2024
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.
serhalp
added a commit
to netlify/angular-runtime
that referenced
this pull request
May 29, 2024
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This configures Renovate to open bump PRs for Remix dependencies in test fixture sites, including unstable releases. This acts as an automated mechanism to run our test suites against Remix releases as soon as possible.
In a later PR, we'll add a notification mechanism for failures on such PRs.
Related Tickets & Documents
FRA-525
QA Instructions, Screenshots, Recordings
I've validated the config file syntax.
We've validated most of this already by testing this out in next-runtime-minimal.
We can't really QA this without merging to main.
See also: