Skip to content

chore(release): 1.36.0 #99

chore(release): 1.36.0

chore(release): 1.36.0 #99

Re-run triggered January 28, 2025 09:26
Status Success
Total duration 29s
Artifacts 5

tag.yml

on: push
build_release_assets  /  build_wheel_sdist
20s
build_release_assets / build_wheel_sdist
Matrix: build_release_assets / Build packages
Push Docker image to Docker Hub
29s
Push Docker image to Docker Hub
Push Docker image to GitHub Packages
32s
Push Docker image to GitHub Packages
Matrix: build_release_assets / linux_package_smoke_tests
push_to_pypi
18s
push_to_pypi
release
9s
release
push_to_cloudsmith
1m 3s
push_to_cloudsmith
Push to GitGuardian taps
11s
Push to GitGuardian taps
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Push Docker image to GitHub Packages
Input 'repository' has been deprecated with message: v2 is now available through docker/build-push-action@v2
Push Docker image to Docker Hub
Input 'repository' has been deprecated with message: v2 is now available through docker/build-push-action@v2
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):