Skip to content

Request to Upgrade Dependent Gems #1786

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

Open
chiraggarg2906 opened this issue May 15, 2025 · 3 comments
Open

Request to Upgrade Dependent Gems #1786

chiraggarg2906 opened this issue May 15, 2025 · 3 comments

Comments

@chiraggarg2906
Copy link

chiraggarg2906 commented May 15, 2025

🤔 What's the problem you're trying to solve?

I’m currently working on upgrading the following cucumber-related gems in my project but am running into issues due to dependency constraints or compatibility problems. Here are the gems and the versions I’m trying to upgrade:

Gem | Current Version | Latest Version

cucumber-core | 13.0.3 | 15.1.0

cucumber-cucumber-expressions | 17.1.0 | 18.0.1

cucumber-gherkin | 27.0.0 | 32.1.1

cucumber-messages | 22.0.0 | 27.2.0

Despite relaxing version constraints in my Gemfile, I’m still unable to complete the upgrade due to dependency resolution conflicts.

Could you please advise if:

  • These versions are intended to work together?

  • Any major breaking changes or known upgrade paths are documented?

  • There are any specific steps or compatibility notes I should follow?

✨ What's your proposed solution?

update the versions

⛏ Have you considered any alternatives or workarounds?

No response

📚 Any additional context?

No response

@luke-hill
Copy link
Contributor

So once cucumber v10 is released you'll be able to directly see all gems updated. For now these aren't designed to work together.

Cucumber v10 will also see a cleaner upgrade path whereby cucumber core will control most of the restrictions. But in essence the gems are reasonably tightly coupled, so you're not meant to upgrade them outside of the constraints that are specified.

@luke-hill
Copy link
Contributor

See #1782 for a PR that relaxes most of the constraints

@chiraggarg2906
Copy link
Author

That great we are waiting for this release.

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

No branches or pull requests

2 participants