Upgrading

We add new features to Cucumber periodically. This means you may want to upgrade to a newer version to take advantage of these new features, as well as any bug fixes.

Versioning

Cucumber follows the SemVer specification for release numbers. Essentially, this means that:

• If only the right-hand (patch) number in the release changes, you don't need to worry.
• If the middle number (minor) number in the release changes, you don't need to worry.
• If the left-hand (major) number changes, you can expect that things might break.

Release

You can read the history file to learn about the changes in every release, and see advice on upgrading across major versions where applicable:

• Cucumber-JVM
  • Changelog https://github.com/cucumber/cucumber-jvm/blob/main/CHANGELOG.md
  • Release notes https://github.com/cucumber/cucumber-jvm/tree/main/release-notes
• Cucumber-JVM-Scale
  • Changelog https://github.com/cucumber/cucumber-jvm-scala/blob/main/CHANGELOG.md
  • Upgrade notes https://github.com/cucumber/cucumber-jvm-scala/tree/main?tab=readme-ov-file#getting-started
• Cucumber-JS
  • Changelog https://github.com/cucumber/cucumber-js/blob/main/CHANGELOG.md
  • Upgrading https://github.com/cucumber/cucumber-js/blob/main/UPGRADING.md
• Cucumber-Ruby
  • Changelog https://github.com/cucumber/cucumber-ruby/blob/main/CHANGELOG.md