dummy python release project
This is a dummy project that exists to test changes to the release process for Python projects at eLife.
It should illustrate how to incorporate a Python project into the Jenkins release process.
It is not a template for Python projects at eLife. Projects come in all shapes and sizes.
usage
- create a new branch
- bump the version number in
setup.py - commit, push, open a PR
- merge PR
CI will then move the changes into approved, then master, then detect that a version change has occured and do a
Pypi release.
Metadata
Release files for elife-dummy-python-release-project 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| elife-dummy-python-release-project-0.0.4.tar.gz | 14.0 kB | Without provenance | Details for elife-dummy-python-release-project-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| elife_dummy_python_release_project-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for elife_dummy_python_release_project-0.0.4-py3-none-any.whl |
Total release size: 28.4 kB
Release files / elife-dummy-python-release-project-0.0.4.tar.gz
| Download URL | elife-dummy-python-release-project-0.0.4.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a234d3be21d6dec4e3c42b40a3a1086cb045218cb65d721168514089809110aa
|
|
BLAKE2b-256 checksum How to use checksums |
de09ced276c787168607426d29d76c613199e66e3dbc5a049860b3bc5dbd99a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / elife_dummy_python_release_project-0.0.4-py3-none-any.whl
| Download URL | elife_dummy_python_release_project-0.0.4-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ec03a8a9f4d3a4ee1ae6cdbfdfe0084a59afe790ee878cbebad551c9e5637f2
|
|
BLAKE2b-256 checksum How to use checksums |
55d5624df318d5ce487b346bdaa795fbfef5bc03b3eb4f1bdab17990d9b611a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for elife-dummy-python-release-project 0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.