Skip to content
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

Encourage following standard Rails upgrade process #34

Merged
merged 2 commits into from
Jan 29, 2025

Conversation

yndajas
Copy link
Member

@yndajas yndajas commented Jan 29, 2025

It's recommended to follow the standard upgrade process when bumping Rails by a minor or major version

This updates our Renovate config to:

  • avoid automerging minor version bumps for Rails (only the internal config is changed, since our default config doesn't automerge minor bumps)
  • provide a warning/reminder about following the process in PR bodies for matching upgrades

An example of an app that's missed changes because of automerging minor Rails upgrades: https://github.com/dxw/ruby-developer-worksim-template/pull/151 (see the second, third, and fourth commits)

There's a [standard process][standard-process] to follow when bumping
Rails by a minor or major version. Without following this, apps can end
up with the version of Rails they're running being out of sync with
their config, database schema, and the defaults that get loaded

We already require approval for major version bumps to any package; this
should additionally make approval required for minor Rails bumps

Note that this only affects apps using the internal config - our default
config requires approval for all minor bumps

[standard-process]: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#the-upgrade-process
This should add a note to the PR body for major and minor Rails upgrades
to remind developers to follow the [standard Rails upgrade
process][standard-process]

[standard-process]: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#the-upgrade-process
@yndajas yndajas force-pushed the dont-automerge-minor-rails branch from 7a8cd70 to 8f0fae0 Compare January 29, 2025 14:32
Copy link
Member

@jacksonj04 jacksonj04 left a comment

Choose a reason for hiding this comment

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

I hadn't even clocked you could get it to leave stuff in the PR body. Nice!

@yndajas
Copy link
Member Author

yndajas commented Jan 29, 2025

I hadn't even clocked you could get it to leave stuff in the PR body. Nice!

It only occurred to me to look for that option when beginning to write in the commit message that devs would still need to remember to do it!

@yndajas yndajas merged commit 074dee3 into main Jan 29, 2025
2 checks passed
@yndajas yndajas deleted the dont-automerge-minor-rails branch January 29, 2025 15:33
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