Skip to content

Comments

Update development dependencies#1725

Merged
neilvcarvalho merged 2 commits intomainfrom
nc-update-dependencies
Jan 27, 2025
Merged

Update development dependencies#1725
neilvcarvalho merged 2 commits intomainfrom
nc-update-dependencies

Conversation

@neilvcarvalho
Copy link
Member

@neilvcarvalho neilvcarvalho commented Jan 24, 2025

We have some outdated dependencies, and are seeing failures on the CI environment for Rails 6.1.

Most of the errors happened due to locked dependencies that are incompatible with some Ruby versions. That was happening because we added the Appraisals lockfiles to the version control, which isn't recommended. Each Ruby version (combined with each Appraisal) should resolve the dependencies themselves, downloading the latest compatible version.

I also updated all dependencies from the gemspec to their latest version. From now on, Dependabot should pick whatever dependencies are updated and we'll know if some of them broke anything. The dependencies were updated using Ruby 3.3, as Ruby 3.4 has a failed spec that I'll investigate in the near future.

@neilvcarvalho neilvcarvalho force-pushed the nc-update-dependencies branch 4 times, most recently from ca67cbf to e7fe15f Compare January 24, 2025 21:10
@neilvcarvalho
Copy link
Member Author

I just noticed a very important notice on the Appraisals README.md:

Version Control
When using Appraisal, we recommend you check in the Gemfiles that Appraisal generates within the gemfiles directory, but exclude the lockfiles there (*.gemfile.lock.) The Gemfiles are useful when running your tests against a continuous integration server.

That makes things way easier.

We've been ignoring an important note from the Appraisals README:

> When using Appraisal, we recommend you check in the Gemfiles that
Appraisal generates within the gemfiles directory, but exclude the
lockfiles there (*.gemfile.lock.) The Gemfiles are useful when running
your tests against a continuous integration server.

Removing the gemfiles makes things way easier for us, since each Ruby
version will resolve the dependencies based on their restrictions.
@neilvcarvalho neilvcarvalho force-pushed the nc-update-dependencies branch from 5487cad to 2c5c050 Compare January 24, 2025 22:38
@neilvcarvalho neilvcarvalho force-pushed the nc-update-dependencies branch from 2c5c050 to 05425ed Compare January 24, 2025 22:40
@neilvcarvalho neilvcarvalho changed the title Update test matrix dependencies Update dependencies Jan 24, 2025
@neilvcarvalho neilvcarvalho changed the title Update dependencies Update development dependencies Jan 24, 2025
@@ -0,0 +1,6 @@
# Auto generated files with errors to ignore.
Copy link
Member Author

Choose a reason for hiding this comment

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

An alternative to adding a TODO file is locking standard to a specific version. I added this because it's outside the scope of this PR.

@neilvcarvalho neilvcarvalho merged commit af56722 into main Jan 27, 2025
27 checks passed
@neilvcarvalho neilvcarvalho deleted the nc-update-dependencies branch January 27, 2025 12:20
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