Skip to content

Upgrade to Resonant v0.48.1#397

Merged
brianhelba merged 1 commit intomainfrom
resonant-upgrade
Mar 9, 2026
Merged

Upgrade to Resonant v0.48.1#397
brianhelba merged 1 commit intomainfrom
resonant-upgrade

Conversation

@brianhelba
Copy link
Member

No description provided.

@brianhelba
Copy link
Member Author

@naglepuff @BryonLewis I met with @bradking earlier today, who helped me to get the Mend Renovate Community service authorized to run on this repo (which provides us with a free robot for actually running Renovate to scan and make PRs). As a future note, while Resonant now contains the config for Renovate, you still need to set up the Mend robot if it's not installed on a GitHub organization.

I'll merge this now, which should create a new always-open issue for tracking dependency issues. The issue is interactive, so we can check boxes within it to trigger Renovate to run on-demand.

Rather than wait for the next scheduled Renovate run (on Sunday night by default), I'll also go ahead and request the PRs to be created now. Then we can discuss an actual upgrade plan (including whether we want to split out some dependencies to separately upgrade or fully pin) in the particular PRs.

@brianhelba brianhelba merged commit 026f0fa into main Mar 9, 2026
6 checks passed
@brianhelba brianhelba deleted the resonant-upgrade branch March 9, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants