newrelic-deploy
Install
$ pip install newrelic-deploy
Create new revision
To create a new release, you need to edit the setup.py file, stating the number of the new version.
After you merge, the Travis CI pipeline will automatically publish the new version at https://pypi.org/project/newrelic-deploy/
Using
Running:
$ newrelic-deploy --key NEWRELIC_KEY --app APP_ID
Metadata
Release files for newrelic-deploy 0.0.6
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 |
|---|---|---|---|---|
| newrelic_deploy-0.0.6.tar.gz | 2.0 kB | Without provenance | Details for newrelic_deploy-0.0.6.tar.gz |
Release files / newrelic_deploy-0.0.6.tar.gz
| Download URL | newrelic_deploy-0.0.6.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd88454452fc9037edbaf206f8896b205ba88ff2b9a372ea66ca8e15ae3545f5
|
|
BLAKE2b-256 checksum How to use checksums |
643f41af0f0f496d634f6ff025a695daf5a5abcaa7edf258db0cad0a6c43f93d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/53.0.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.6.7
|
Security for newrelic-deploy 0.0.6
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.