Releases: gidgethub/gidgethub
Releases · gidgethub/gidgethub
5.3.0
5.2.1
5.2.0
5.1.0
-
Use
X-Hub-Signature-256
header for webhook validation when available.
(PR #160). -
The documentation is now built using Sphinx v>= 4.0.0.
(Issue #143) -
gidgethub.abc.GitHubAPI.getiter
now acceptsiterable_key
parameter
in order to support the Checks API.
(Issue #164) -
Accept HTTP 202 ACCEPTED as successful.
(PR #174)
5.0.1
- Drop the
machine-man-preview
header fromgidgethub.apps.get_installation_access_token
because it is out of preview. The machine-man-preview is no longer required as of August 20, 2020. Discussion #155
5.0.0
- Add
gidgethub.routing.Router.fetch
for obtaining a frozenset of functions
registered to the router that the event would be called on.
Issue #74. - Add support for GitHub Actions Environment Files with
gidgethub.actions.setenv
andgidgethub.actions.addpath
.
Issue #137. - Make router callback execution order non-deterministic to avoid relying on
registration order.
Issue #74. - Fix mypy errors in
gidgethub.httpx.GitHubAPI._request
Issue #133. - Make the minimum version of PyJWT be v2.0.0.
4.2.0
gidgethub.abc.GitHubAPI.post()
now accepts content_type parameter. If supplied, thecontent_type
value will be used in the request headers, and the raw form of the data will be passed to the request. If not supplied, by default the data will be parsed as JSON, and the“application/json”
content type will be used. (Issue #115).
v4.1.1
Prep for 4.1.1 release (#126)
4.1.0
- Introduce
gidgethub.apps
. - Introduce
gidgethub.apps.get_installation_access_token()
for obtaining an installation access token that can be used to authenticate as a GitHub App installation. (Issue #71). - Introduce
gidgethub.apps.get_jwt()
for constructing the JSON Web Token that can be used to access endpoints that require it.
3.3.0
v3.3.0 Try using RTD's default theme