Skip to content

Conversation

@boost-tim
Copy link
Contributor

Worker Rails 7.2
As a Software Developer, I want to upgrade our Rails application from 7.1.5.1 to 7.2 so that we maintain support on the current Rails version

Acceptance Criteria:

  • Rails upgraded to the latest 7.2.x version
  • All dependencies updated to compatible versions
  • Test suite passes with new Rails version
  • Application functions correctly in all environments
  • Security CI job passes without EOL warnings
  • Breaking changes are identified and addressed
  • Database migrations run successfully
  • Performance remains stable or improves

@github-actions
Copy link

Code quality score

Lovely, the code quality is unchanged for this PR 😊

Ruby file count Similarity score (flay) ABC complexity (flog) Code smells (reek) TOTALS
base 63 1.4 7.92 18.35 27.67
this branch 63 1.4 7.92 18.35 27.67
difference 0 0.0 0.0 0.0 0.0

Gemfile Outdated
# gem 'supplejack_common', path: '~/Dev/supplejack/gems/supplejack_common'
# gem 'supplejack_common', github: 'DigitalNZ/supplejack_common', branch: 'pm/upgrade'
gem 'supplejack_common', github: 'DigitalNZ/supplejack_common', tag: 'v3.0.2'
gem 'supplejack_common', github: 'DigitalNZ/supplejack_common', branch: 'tw/rails-7-2'

Choose a reason for hiding this comment

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

Will this need changed before you merge? Do the other 2 commented out lines need removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep I'll need to update this once the supplejack common PR is merged. Good point about commented lines, we can probably remove these.

bin/setup Outdated
system! "bin/rails restart"

# puts "\n== Configuring puma-dev =="
# system "ln -nfs #{APP_ROOT} ~/.puma-dev/#{APP_NAME}"

Choose a reason for hiding this comment

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

question: do you need to include this commented out or can you remove?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good question, it was added by 'rails app:update' could probably remove

end

it 'does not flush records if a harvest failure occured' do
it 'does not flush records if a harvest failure occurred' do

Choose a reason for hiding this comment

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

nice!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍

config.force_ssl = true

# Skip http-to-https redirect for the default health check endpoint.
# config.ssl_options = { redirect: { exclude: ->(request) { request.path == "/up" } } }

Choose a reason for hiding this comment

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

same as above

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good question, it was added by 'rails app:update' could probably remove

@boost-tim boost-tim merged commit 15c8f84 into main Oct 14, 2025
6 checks passed
@boost-tim boost-tim deleted the tw/rails-7-2 branch October 14, 2025 22:50
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.

4 participants