chore: updates related to release process #41
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
AtofStryker
approved these changes
Aug 8, 2023
| @@ -68,6 +68,8 @@ There are a few basic ground-rules for contributors: | |||
|
|
|||
| Declaring formal releases remains the prerogative of the project maintainer. | |||
|
|
|||
| This package uses semantic versioning and [semantic-release](https://github.com/semantic-release/semantic-release) to auto-publish releases to npm upon merge into the master branch. | |||
|
Thanks for cleaning this up! The published package is fine. I just noticed the wrong version logged in https://github.com/cypress-io/request/actions/runs/5797590779/job/15713444906 for the v3.0.0 release, which had me scratching my head! 🙂 |
|
🎉 This PR is included in version 3.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist:
npm testlocally and all tests are passing.PR Description
Some updates related to how this package is released.
release.shsince that was related to the old way of releasingpackage.jsonversion to0.0.0-development. This is standard when using semantic-release, since it does not commit the new version back to the repo when publishing it. This way the committed version isn't wrong and there's no need to manually update the version when there is a new release.