Skip to content

Conversation

yukideluxe
Copy link
Member

@yukideluxe yukideluxe commented Jul 11, 2025

Hello!

I am opening this PR to be able to unblock #698.

The goal is to be able to always develop against the latest version of money Gem (or a branch if you wish so) instead of a published version (because that can still take a few days!)

I also learned about eval_gemfile today and adjusted the rails gemspecs to avoid duplication inspired but what @sunny suggested here #716 (comment) 😳

PS: I removed the Guard* gems, what is that? the Guardfile rings a bell, but I don't remember ever using that, and guard-rspec hasn't been updated in FOREVER so I just 🧹
PS2: I haven't forgotten about the mongo tests... 😇

strategy:
matrix:
ruby-version: ['3.0', '3.1', '3.2', '3.3', '3.4']
ruby-version: ['3.1', '3.2', '3.3', '3.4']
Copy link
Member Author

Choose a reason for hiding this comment

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

related #717 (comment) and also because the last money requires at least 3.1 ✌🏻

Copy link
Member

@sunny sunny left a comment

Choose a reason for hiding this comment

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

Great use of eval_gemfile, it’ll help reduce duplication!

Guard can be nice… but it is of no use when none of the maintainers use it 😁

Co-authored-by: Sunny Ripert <[email protected]>
@yukideluxe yukideluxe merged commit 8c7c5e1 into main Jul 11, 2025
4 checks passed
@yukideluxe yukideluxe deleted the jl-more-dev-improvements branch July 11, 2025 16:01
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