Skip to content
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.

Sign up for GitHub

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

Prepare release 2.2.0 #131

Merged
merged 2 commits into from
Oct 24, 2024
Merged

Prepare release 2.2.0 #131

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d18b85c
Prepare release 2.2.0
nicoddemus Oct 24, 2024
c1dcecc
Trigger main workflow also on tags
nicoddemus Oct 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ on:
push:
branches:
- master
tags:
- "v[0-9]+.[0-9]+.[0-9]+"

pull_request:

Expand Down Expand Up @@ -64,6 +66,10 @@ jobs:
user: __token__
password: ${{ secrets.pypi_token }}
attestations: true
- name: GitHub Release
uses: softprops/[email protected]
with:
files: dist/*

sonarcloud:

Expand Down
6 changes: 4 additions & 2 deletions CHANGELOG.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
2.2.0 (UNRELEASED)
------------------
2.2.0
-----

**Release**: 2024-10-24

* ``PriorityCallback`` now has type checking support, similar to ``Callback``, with type checked variants: ``PriorityCallback0``, ``PriorityCallback1``, etc (`#128`_).
* ``UnregisterContext`` is now public, meant to be used in type annotations.
Expand Down
3 changes: 1 addition & 2 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,8 +121,7 @@ Release
-------
A reminder for the maintainers on how to make a new release.

Note that the VERSION should follow the semantic versioning as X.Y.Z
Ex.: v1.0.5
Note that the VERSION should follow the semantic versioning as ``X.Y.Z`` (e.g. ``v1.0.5``).

1. Create a ``release-VERSION`` branch from ``upstream/master``.
2. Update ``CHANGELOG.rst``.
Expand Down
Loading