Test Python Library
Library used to test a new simplified release flow.
Development
A suggested method of development is to use git worktrees.
- From a personal fork, create a new worktree for the bug, feature or chore.
git worktree add feature-a
-
Implement the code changes and commit.
-
Update the CHANGELOG.md to include the change in the "Unreleased" section.
-
Commit, push and create a PR to the upstream repository's main branch.
-
Solicit a code-read from another team member.
-
Upon approval, squash and merge to main.
-
(optional) cleanup by removing the worktree and associated local and remote branch.
If the version was incremented in pyproject.toml, the merge to the main branch will trigger a release to test PyPI (but not production PyPI).
Releasing
Only create a release for actual library updates. Things that do not warrant a release:
- Repository metadata such as README updates, workflow changes, etc.
- Cleanup/refactors
-
Create a new branch "release-x.y.z" When incrementing, follow Semantic Versioning standard.
- Bug fixes: ++ patch version
- Features: ++ minor version
- Breaking Changes: ++ major version
-
Update pyproject.toml with the new version.
-
Update CHANGELOG.md by moving the "Unreleased" items into a new section for the given version (leaving an empty Unreleased section as a template for future updates)
-
Commit, push and create a PR to upstream's main branch Please set the commit message to "Release vx.y.z" with the new version number
-
Obtain approval for release from another team member.
-
Squash and merge (ensure the commit message remains Release vx.y.x).
-
Verify the new version was correctly published to test PyPI and all precautions have been taken to ensure it is functioning as intended.
-
Pull from upstream into your local main branch and tag the commit vx.y.z (the squash and merge will have created a new commit hash)
-
push the tag to upstream, triggering the release to production PyPI.
Metadata
Release files for lkingland-test-pylib 0.1.3
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 |
|---|---|---|---|---|
| lkingland_test_pylib-0.1.3.tar.gz | 5.6 kB | Without provenance | Details for lkingland_test_pylib-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lkingland_test_pylib-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for lkingland_test_pylib-0.1.3-py3-none-any.whl |
Total release size: 12.1 kB
Release files / lkingland_test_pylib-0.1.3.tar.gz
| Download URL | lkingland_test_pylib-0.1.3.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa8f5e8a80c7f3806abeef8f55208b634bc04d2b37c3d507a87a11b154b44c2a
|
|
BLAKE2b-256 checksum How to use checksums |
e8b4790b386e615faf83c777cdea5bd0f8526e027ab75c8bbacd7dc5ab4d003e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / lkingland_test_pylib-0.1.3-py3-none-any.whl
| Download URL | lkingland_test_pylib-0.1.3-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7635bcf0d6c9ab7c86558c70bdf21e8d0fb3702fd34a07e54fe876425de01aa0
|
|
BLAKE2b-256 checksum How to use checksums |
16be51702a0242d05f365e8c6bfbdbe0563f3006846a49ca246ef8adcb83d6a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for lkingland-test-pylib 0.1.3
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.