build: v2.0.0b1 - Githubissues

alcarney commented 3 weeks ago

(Yes, this version number change isn't strictly necessary but the release process (#488) calls for a PR :smile:)

Code review checklist (for code reviewer to complete)

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[ ] Title summarizes what is changing
[ ] Commit messages are meaningful (see this for details)
[ ] Tests have been included and/or updated, as appropriate
[ ] Docstrings have been included and/or updated, as appropriate
[ ] Standalone docs have been updated accordingly

Automated linters

You can run the lints that are run on CI locally with:

poetry install --all-extras --with dev
poetry run poe lint

tombh commented 3 weeks ago

Oh! The release process doesn't require a PR per se, it's just that typically a release will include a bunch of PRs none of which in themselves bump the version. So in this case, seeing as main already contains the correct version bump we can go straight for a release 🛳️

And I'll update #488 to clarify!

alcarney commented 3 weeks ago

Ok done - that was easy! :D

https://pypi.org/project/pygls/2.0.0a1/ https://github.com/openlawlibrary/pygls/releases/tag/v2.0.0a1

tombh commented 3 weeks ago

Awesome 🥹

openlawlibrary / pygls

build: v2.0.0b1 #493

Code review checklist (for code reviewer to complete)

Automated linters