docs: Add and update docs for the 4.0 release#228
Merged
Conversation
3 tasks
Explain what is (and is not) guaranteed to be backwards compatible between minor and patch releases.
Remove references to YAML config and update Extensions example to show referencing the extension by its fully-qualified class name.
Simplify some wording, make it friendlier, improve clarity of the lists of actions.
Simplify some wording, make it friendlier, improve clarity of the lists of actions.
Contributor
Author
| 6. **Check Deprecations:** Run your tests with ``--fail-on-deprecations`` and fix any warnings that appear. | ||
| 7. **Test the New Parser:** Enable the :doc:`GHERKIN_32 parser mode </user_guide/gherkin/parser_mode>` and see if your | ||
| tests still run correctly. If you have issues, you can fix your feature files or use | ||
| ``GherkinCompatibilityMode::LEGACY`` in your config. This mode will be removed in future. |
carlos-granados
approved these changes
Jun 22, 2026
carlos-granados
left a comment
Contributor
There was a problem hiding this comment.
Outstanding work, @acoulton, just a single tiny comment, no need to ask for a new review when you fix it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes details of YAML configuration and PHPDoc annotations, which we no longer support.
Provides update notes for Behat 4.0 - I have focused on spelling out the steps for end users to follow, and the most significant changes that we expect will affect all extension authors. There are other changes that might affect a minority of extensions but I think it's OK to point to the CHANGELOG for these. We can always add more guidance later if we see people having common issues.
I've also only given brief details about using Rector and links to their own documentation. I don't think we need to repeat that in our own docs, and it avoids us getting out of sync with any changes in Rector.
Also documents our approach to Backwards Compatibility, following the PHPStan conventions, as discussed in Behat/Behat#1745 and applied in Behat/Behat#1807.