Skip to content
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

chore(deps): update dependency @cucumber/compatibility-kit to v17 #264

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cucumber/compatibility-kit ^16.0.0 -> ^17.0.0 age adoption passing confidence

Release Notes

cucumber/compatibility-kit (@​cucumber/compatibility-kit)

v17.0.0

Compare Source

Added
  • Add TestRunStarted.id, TestCase.testRunStartedId and TestRunFinished.testRunStartedId to reference messages
  • Add Hook.type to reference messages

v16.3.0

Compare Source

Added
  • Add example for empty scenario (#​103)
Removed
  • [Ruby] The reference to the messages gem is no longer required

v16.2.0

Compare Source

Changed
  • [Ruby] Permit messages up to v28 (#​107)

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/cucumber-compatibility-kit-17.x branch 3 times, most recently from 83c8675 to 97ea359 Compare November 15, 2024 20:20
@renovate renovate bot force-pushed the renovate/cucumber-compatibility-kit-17.x branch from 97ea359 to f841235 Compare November 15, 2024 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants