TODO
Release history
1.0.1
- Remove biomapas/cicd-full image from pipelines.
1.0.0
- Upgrade CDK support from v1 to v2.
- Upgrade GitHub pipelines checkout version from v2 to v3.
- Set GitHub pipelines node version 18.
- Set GitHub pipelines python version 3.10.
0.0.4
- Increase the function timeout.
0.0.3
- Update boto3 requirement.
0.0.2
- Add more docstrings.
0.0.1
- Initial build.
Metadata
Release files for b-stage-deployment 1.0.1
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 | |
|---|---|---|---|---|
| b_stage_deployment-1.0.1.tar.gz | 10.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| b_stage_deployment-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / b_stage_deployment-1.0.1.tar.gz
| Download URL | b_stage_deployment-1.0.1.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba6632ec48e97d5fcf0f73115e87df95221e0e34113262f1c2e2100a5c13e891
|
|
BLAKE2b-256 checksum How to use checksums |
823ea3ad175783d772e2e3543125b5449a5dee095ca4dcfe2d8a6619c884dd59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / b_stage_deployment-1.0.1-py3-none-any.whl
| Download URL | b_stage_deployment-1.0.1-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
044384306bbedf3864e79602a93dda4130be075bc0ec76f30394499d647ca28e
|
|
BLAKE2b-256 checksum How to use checksums |
7ec1c8636e519f33106b29094df5a8c9e94992689103cf6027ca282dfdedd5bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for b-stage-deployment 1.0.1
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.