After releasing XY we should update composer.json in master to point to a new tag (from https://github.com/moodlehq/moodle-behat-extension.git master branch) according to the moodle development version (3.34.0 for Behat 3 and Moodle 3.4dev for example - this issue).

Detailed process:

https://docs.moodle.org/dev/Release_process#3_weeks_after

Verify the new version has been released in packagist (it happens weekly by default or under demand if a package maintainer is asked).

To regenerate the composer.lock file, delete it, delete vendor and, using the lower php version supported by the .dev Moodle, run composer update.

Ensure changes related to the extension are ok in the .lock file. It will come also with updates to many of the dependencies. Run behat tests and phpunit tests to confirm they work ok.

Note: it's possible to automate it using the packagist hook @ github and surely we'll end doing that. Just let's get used to managing the behat-extension, its branches and tags, using the manual "update" @ packagist. And once we are used... move to automate.