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

Rails 7.2 compatibility #1477

Closed
wants to merge 1 commit into from
Closed

Conversation

theodorton
Copy link

@theodorton theodorton commented Jun 2, 2024

  • Wrote good commit messages.
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests. - Not relevant; refactoring to support Rails 7.2
  • Added an entry to the Changelog if the new
    code introduces user-observable changes. - Not relevant; refactoring to support Rails 7.2
  • The PR relates to only one subject with a clear title
    and description in grammatically correct, complete sentences.

@fatkodima
Copy link
Contributor

fatkodima commented Jun 15, 2024

Can you please squash your commits into 1? You also need to update this line -

ACTIVERECORD_LT = "< 7.2" # not enforced in gemspec

That CI failure regarding coverage - these coverage metrics are pretty pointless imo, I would prefer to just remove it from the project.

@theodorton theodorton force-pushed the rails-7-2 branch 2 times, most recently from 5ffca52 to 5a62060 Compare June 17, 2024 08:23
@theodorton
Copy link
Author

I've fixed the compatibility spec, added the new appraisal to the CI matrix and squashed.

@theodorton theodorton force-pushed the rails-7-2 branch 2 times, most recently from baedbf3 to 844dce1 Compare June 17, 2024 08:26
@fatkodima fatkodima mentioned this pull request Aug 11, 2024
10 tasks
@arikarim
Copy link

any update on this please?

@theodorton
Copy link
Author

Updated appraisal to use the official Rails 7.2 release. I can't do much about the coverage metrics that @fatkodima already mentioned.

@jaredbeck Is there any more work needed from my side to get this to a mergeable state?

@veganstraightedge
Copy link

Hi paper trail gem folks 👋🏻 i'm adding my voice to the chorus of encouragement to merging this PR or the other one #1485

@kriom
Copy link

kriom commented Aug 29, 2024

Likewise, hello people from paper trail gem, I also add my voice and encouragement to merge this PR 🫶

@@ -59,11 +59,14 @@ jobs:
# have set this up with each database as a separate job, but then we'd be
# duplicating the matrix configuration three times.
matrix:
gemfile: [ 'rails_6.1', 'rails_7.0', 'rails_7.1' ]
gemfile: [ 'rails_6.1', 'rails_7.0', 'rails_7.1', 'rails_7.2' ]

# To keep matrix size down, only test highest and lowest rubies.
# See "Lowest supported ruby version" in CONTRIBUTING.md
ruby: [ '3.0', '3.2' ]
Copy link

@joshRpowell joshRpowell Aug 29, 2024

Choose a reason for hiding this comment

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

@gurgelrenan
Copy link
Member

gurgelrenan commented Sep 1, 2024

Let's focus on #1485 . I will close this P.R. @theodorton could you please check if you could improve #1485 ?

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.

7 participants