-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
docs: add RELEASING.md doc #488
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# How To Make A New Release Of PyGLS | ||
|
||
1. Update the version number in `pyproject.toml` | ||
|
||
- Try to follow https://semver.org/ | ||
- Commit message title should be something like: `build: v1.3.0` | ||
- Typically you'll want to make a dedicated PR for the version bump. But if a previous PR has already merged the wanted version bump into main, then a new PR is not necessary. | ||
- Example PR for a release https://github.com/openlawlibrary/pygls/pull/434 | ||
- Merge the PR | ||
|
||
2. Create a Github Release | ||
|
||
- Goto https://github.com/openlawlibrary/pygls/releases/new | ||
- In the "Choose a tag" dropdown button, type the new version number. | ||
- Click the "Generate release notes" button. | ||
- Generating release notes does not require making an actual release, so you may like to copy and paste the output of the release notes to make the above release PR more informative. | ||
- If it's a pre-release, remember to check the "Set as a pre-release" toggle. | ||
- Click the green "Publish release button". | ||
- Once the Github Release Action is complete (see https://github.com/openlawlibrary/pygls/actions), check https://pypi.org/project/pygls/ to verify that the new release is available. | ||
|
||
## Notes | ||
|
||
- `CHANGELOG.md` and `CONTRIBUTORS.md` are automatically populated in the Github Release Action. | ||
- PyPi automatically detects beta and alpha versions from the version string, eg `v1.0.0a`, and prevents them from being the latest version. In other words, they're made publicly available but downstream projects with loose pinning (eg `^1.0.0`) won't automatically install them. |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a note to check the "Set as a pre-release" button if required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, done ☑️