Purpose

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.

Rationale

This could probably also be avoided by running the entrypoint as a non privileged user, but this would require using sudo or alternative solutions for running e.g. the git config --system command.
In general the usage of the root user isn't really a problem for this action so this seems to be the most straightforward way to workaound the permission issues.

How did you test?

• Defined a workflow using the latest v9 of python-semantic-release with an additional checkout at the end: kwevers/stunnel@3466e0e
• Workflow completes fine: https://github.com/kwevers/stunnel/actions/runs/12914296597
• Add custom commit parser: kwevers/stunnel@0107a25
• Workflow fails with permissions errors on the pyc file: https://github.com/kwevers/stunnel/actions/runs/12914411688
• Reference https://github.com/kwevers/python-semantic-release/tree/bugfix/python-byte-code which disables bytecode writing: kwevers/stunnel@00cf3f9
• Workflow works fine: https://github.com/kwevers/stunnel/actions/runs/12914460530

How to Verify

See linked actions in testing section.