Skip to content

feat: Disable writing Python bytecode #217

feat: Disable writing Python bytecode

feat: Disable writing Python bytecode #217

Re-run triggered January 23, 2025 21:28
Status Failure
Total duration 1m 22s
Artifacts 1

ci.yml

on: pull_request
Evaluate changes
8s
Evaluate changes
commitlint
11s
commitlint
Matrix: validate / test-linux
Matrix: validate / test-windows
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
commitlint
You have commit messages with errors ⧗ input: feat: Disable writing Python bytecode Permission issues can occur on the Python bytecode files as the container entrypoint is being run as the root user. When e.g. using a custom parser the bytecode file will be owned by the root user instead of the user running the action. This can cause subsequent steps to fail. For example when running actions/checkout after python-semantic-release it will try to do a `git clean -ffdx` which will fail to remove the pyc file. ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
Evaluate changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
commitlint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
validate / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
validate / Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size Digest
dist Expired
375 KB
sha256:3eca0dd5aa723448ae7d3ce02627dcb10f1e79794bcb4ccaeefcbc1a08e265eb