Skip to content

fix: verhindere automatische Übergänge von 0.x.x auf 1.0.0 in der Sem… #33

fix: verhindere automatische Übergänge von 0.x.x auf 1.0.0 in der Sem…

fix: verhindere automatische Übergänge von 0.x.x auf 1.0.0 in der Sem… #33

Triggered via push September 1, 2025 20:23
Status Success
Total duration 2m 38s
Artifacts 6
🐍 Python Semantic Release Pipeline  /  🧪 Tests & Quality
48s
🐍 Python Semantic Release Pipeline / 🧪 Tests & Quality
🐍 Python Semantic Release Pipeline  /  ...  /  🔐 Security Analysis
16s
🐍 Python Semantic Release Pipeline / 🔐 Security Analysis / 🔐 Security Analysis
🐍 Python Semantic Release Pipeline  /  ...  /  📄 License Analysis
1m 33s
🐍 Python Semantic Release Pipeline / 📄 License Compliance / 📄 License Analysis
🐍 Python Semantic Release Pipeline  /  ...  /  🔍 PR Quality Gates
🐍 Python Semantic Release Pipeline / PR Quality Gate / 🔍 PR Quality Gates
🐍 Python Semantic Release Pipeline  /  🚀 Semantic Release
19s
🐍 Python Semantic Release Pipeline / 🚀 Semantic Release
🐍 Python Semantic Release Pipeline  /  ...  /  Generate Documentation
5s
🐍 Python Semantic Release Pipeline / 📚 Update Documentation / Generate Documentation
🐍 Python Semantic Release Pipeline  /  📤 Publish to PyPI
19s
🐍 Python Semantic Release Pipeline / 📤 Publish to PyPI
🐍 Python Semantic Release Pipeline  /  ...  /  Validate Documentation
4s
🐍 Python Semantic Release Pipeline / 📚 Update Documentation / Validate Documentation
🐍 Python Semantic Release Pipeline  /  ...  /  Generate Security Policy
6s
🐍 Python Semantic Release Pipeline / 🔒 Update Security Policy / Generate Security Policy
🐍 Python Semantic Release Pipeline  /  ...  /  Validate Security Policy
5s
🐍 Python Semantic Release Pipeline / 🔒 Update Security Policy / Validate Security Policy
🐍 Python Semantic Release Pipeline  /  📊 Pipeline Summary
3s
🐍 Python Semantic Release Pipeline / 📊 Pipeline Summary
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
gitguardian-security-reports Expired
1.36 KB
sha256:6bcee874f22bb619f956897e47a8b415a8bca1e94362f965924edd6f4cf03a25
gitleaks-results.sarif
431 Bytes
sha256:25513806312426ed1836bfb7488925f57a0e05bd91823275bb5c6bf9fd15711f
license-compliance-report Expired
7.23 KB
sha256:c4485693c8a28767919a113ba56aa4513384b2e2a373fee200ef2ec9dc368c4d
license-compliance-reports Expired
7.23 KB
sha256:c4485693c8a28767919a113ba56aa4513384b2e2a373fee200ef2ec9dc368c4d
python-wheel-33 Expired
103 KB
sha256:13768d5b73b878088ec5fdd88acc5d9e81f65fcda3991dbe24bbc2f7b151ec06
security-scan-reports Expired
2.41 KB
sha256:61687bc6d57bd257e392730daa9c7fed13324dca6bc868622404c17bba179105