Create releasing guidelines

glibas commented 3 months ago

🤔 What's changed?

Adding RELEASING guidelines.

⚡️ What's your motivation?

Was hard to figure out the release process.

🏷️ What kind of change is this?

:bank: Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)

♻️ Anything particular you want feedback on?

Nice and simple release process, just needs documenting.

📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[ ] I've changed the behaviour of the code
- [ ] I have added/updated tests to cover my changes.
[ ] My change requires a change to the documentation.
- [X] I have updated the documentation accordingly.
[ ] Users should know about my change
- [ ] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

This text was originally generated from a template, then edited by hand. You can modify the template here.

github-actions[bot] commented 3 months ago

Go API Changes

# summary
Inferred base version: v0.14.0
Suggested version: v0.14.1

codecov[bot] commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (244de82) 83.21% compared to head (45417f5) 83.21%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #608 +/- ## ======================================= Coverage 83.21% 83.21% ======================================= Files 28 28 Lines 3413 3413 ======================================= Hits 2840 2840 Misses 458 458 Partials 115 115 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

cucumber / godog