chore(deps): update dependency cucumber_messages to v19 - autoclosed

[renovate]

This PR contains the following updates:

Package	Update	Change
cucumber_messages	major	~> 15.0 -> ~> 19.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[mpkorstanje]

@WannesFransen1994 could you please have a look at this?

[WannesFransen1994]

I'll take a look at it this evening!

[mpkorstanje]

Cheers! Appreciated!

[WannesFransen1994]

It seems that with the new releases of messages, something went wrong with the Elixir release since the generated/compiled files aren't included in this release. (Current messages version is still generating the files based on protox, but aren't included in the published package)

Since the new messages version (based on the json schemas) won't be compatible with this gherkin version, i'd suggest keeping the old messages version for now. Then when the new messages version (cucumber/messages#29) is released correctly, we can correct the current gherkin implementation to the latest messages?

Unless I can do something else to make this process "smoother", I'll leave it to you @mpkorstanje . Sadly i'm not so familiar with the current release process with the polyglot repository (nor am i sure that I should be the one doing that), but let me know if I can do anything else!

[mpkorstanje]

Unfortunately @aurelien-reeves is no longer working for SmartBear and because of that no longer contributing to Cucumber. Now I do not know why cucumber/messages#29 wasn't merged. Perhaps because cucumber/messages#29 (review) hasn't been answered.

If you could get that PR into a merge-able state (I'll leave the exact definition of that up to you) then I can see it merged and released.

[mpkorstanje]

The new release process is linked to from RELEASING.md and can be found here: https://github.com/cucumber/.github/blob/main/RELEASING.md. The process is really light weight and takes about 10 seconds to perform.

TL;DR: Anyone who can push to main can prepare a release, only a few people can perform the release.

[WannesFransen1994]

Thank you for the info. I'll make the branch merge-able this weekend and if there are any uncertainties, I'll mention it on the next weekly meeting (or ask it on the PR comments).

[mpkorstanje]

Cheers, and no rush!