Skip to content

🐙 chore: enhance CI/CD, versioning, and testing setup #6

🐙 chore: enhance CI/CD, versioning, and testing setup

🐙 chore: enhance CI/CD, versioning, and testing setup #6

Triggered via push August 12, 2025 05:34
Status Success
Total duration 1m 42s
Artifacts 1

3_ci-cd.yaml

on: push
Run full test suite  /  filter
4s
Run full test suite / filter
Run full test suite  /  ...  /  lint
Run full test suite / lint / lint
Run full test suite  /  ...  /  unit-tests
Run full test suite / unit-tests / unit-tests
Run full test suite  /  ...  /  Run Docker-based tests
Run full test suite / docker-tests / Run Docker-based tests
Run full test suite  /  ...  /  Run Kubernetes-based tests
Run full test suite / kubernetes-tests / Run Kubernetes-based tests
Run full test suite  /  Combine coverage reports and report
0s
Run full test suite / Combine coverage reports and report
Run full test suite  /  Did all tests pass?
4s
Run full test suite / Did all tests pass?
Release Python Package and Docker Image  /  params
3s
Release Python Package and Docker Image / params
Release Python Package and Docker Image  /  ...  /  build
28s
Release Python Package and Docker Image / build-python-package / build
Release Python Package and Docker Image  /  ...  /  build-docker
40s
Release Python Package and Docker Image / build-docker-image / build-docker
Release Python Package and Docker Image  /  ...  /  create-release
3s
Release Python Package and Docker Image / create-github-release / create-release
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
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):
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
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.

Artifacts

Produced during runtime
Name Size Digest
CatchNip~mcp-selenium-grid~MU2XW8.dockerbuild Expired
56.4 KB
sha256:877be43e9967bae1205b43858962be4ff68905c2811c5950694379ea4c3e5d62