python-semantic-release/Python Semantic Release - Publish
Publish Artifacts & Assets to GitHub Releases
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| config_file | Path to a custom semantic-release configuration file. By default, an empty string will look for a pyproject.toml file in the current directory. This is the same as passing the `-c` or `--config` parameter to semantic-release. | no | "" |
| directory | Sub-directory to change into before running semantic-release publish | no | . |
| github_token | GitHub token used to upload artifacts. Requires permission to create and edit releases. | yes | — |
| no_operation_mode | If set to true, the github action will pass the `--noop` parameter to semantic-release. This will cause semantic-release to run in "no operation" mode. See the documentation for more information on this parameter. | no | false |
| tag | The tag corresponding to the GitHub Release that the artifacts should be published to. Defaults to 'latest', in which case the latest tag will be identified by Python Semantic Release and used to publish to. | no | — |
| verbosity | Set the verbosity level of the output as the number of -v's to pass to semantic-release. 0 is no extra output, 1 is info level output, 2 is debug output, and 3 is silly debug level of output. | no | 1 |
Outputs
no outputs