Skip to content

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

Conversation

serhalp
Copy link
Member

@serhalp serhalp commented May 24, 2024

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:

@serhalp serhalp requested a review from a team as a code owner May 24, 2024 15:29
Copy link

netlify bot commented May 24, 2024

Deploy Preview for remix-edge ready!

Name Link
🔨 Latest commit 655170e
🔍 Latest deploy log https://app.netlify.com/sites/remix-edge/deploys/6650d0ee77dfe30008da2424
😎 Deploy Preview https://deploy-preview-355--remix-edge.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented May 24, 2024

Deploy Preview for remix-serverless ready!

Name Link
🔨 Latest commit 655170e
🔍 Latest deploy log https://app.netlify.com/sites/remix-serverless/deploys/6650d0ee77742700089ef6bd
😎 Deploy Preview https://deploy-preview-355--remix-serverless.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added the type: chore work needed to keep the product and development running smoothly label May 24, 2024
@serhalp serhalp force-pushed the serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause branch from 023a84f to 23c5e88 Compare May 24, 2024 15:30
@serhalp serhalp force-pushed the serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause branch from 23c5e88 to 43264f0 Compare May 24, 2024 16:34
@serhalp serhalp enabled auto-merge (squash) May 24, 2024 16:34
@serhalp serhalp requested a review from mrstork May 24, 2024 16:34
@serhalp serhalp force-pushed the serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause branch from 43264f0 to 655170e Compare May 24, 2024 17:39
Copy link
Contributor

@mrstork mrstork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@serhalp serhalp merged commit b8d699f into main May 24, 2024
13 checks passed
@serhalp serhalp deleted the serhalp/fra-525-notify-first-responder-when-new-framework-releases-cause branch May 24, 2024 17:44
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
Labels
type: chore work needed to keep the product and development running smoothly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants