Skip to content

use semantic versioning #280

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Dec 30, 2023
Merged

use semantic versioning #280

merged 1 commit into from
Dec 30, 2023

Conversation

ursfassler
Copy link
Contributor

Summary

Use version numbers that follow MAJOR.MINOR.PATCH as specified in by semantic versioning (https://semver.org/).

Details

Motivation and Context

Follow the "standard" for versioning.

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

  • It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
  • I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
  • I've added tests for my code.
  • I have verified whether my change requires changes to the documentation
  • My change either requires no documentation change or I've updated the documentation accordingly.
  • My branch has been rebased to main, keeping only relevant commits.

Use version numbers that follow MAJOR.MINOR.PATCH as specified in by
semantic versioning (https://semver.org/).
@ursfassler ursfassler merged commit 9df1a01 into cucumber:main Dec 30, 2023
@ursfassler ursfassler deleted the semver branch December 30, 2023 18:49
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant