The cloudmesh bumpversion command
Manual Page
Usage:
bumpversion patch
bumpversion minor
bumpversion major
bumpversion info
bumpversion set --version=VERSION
bumpversion --config=YAML --version=VERSION
Manages bumping the version for cloudmesh
Arguments:
VERSION the version number to set
YAML the yaml file name
Options:
--version=VERSION the version number to set
--config=YAML the YAML FILE
Description:
this program modifies the following files.
It reads the VERSION form the ./VERSION file
the number is of the form MAJOR.MINOR.PATCH
It increase the specified number
It writes the number to the files
./VERSION
./cloudmesh/cloudmesh-PACKAGE/__version__.py
> bumpversion patch
> increments the third number
> bumpversion minor
> increments the second number
> bumpversion mayor
> increments the first number
> bumpversion info
> lists the numbers and identifies if one of them is wrong
> bumpversion set --version=VERSION
> sets the version number to the spcified number
> bumpversion --config=YAML --version=VERSION
> sets the versions in the files specifed in the yaml file
> Example: bumpversion.yaml
>
> bumpversion:
> - cloudmesh/bumpversion/__version__.py
> - VERSION
Manual Page
Command bar
===========
::
Usage:
bar --file=FILE
bar list
bar [--parameter=PARAMETER] [--experiment=EXPERIMENT] [COMMAND...]
This command does some useful things.
Arguments:
FILE a file name
PARAMETER a parameterized parameter of the form "a[0-3],a5"
Options:
-f specify the file
Description:
> cms bar --parameter="a[1-2,5],a10"
> example on how to use Parameter.expand. See source code at
> https://github.com/cloudmesh/cloudmesh-bar/blob/main/cloudmesh/bar/command/bar.py
> prints the expanded parameter as a list
> ['a1', 'a2', 'a3', 'a4', 'a5', 'a10']
> bar exp --experiment=a=b,c=d
> example on how to use Parameter.arguments_to_dict. See source code at
> https://github.com/cloudmesh/cloudmesh-bar/blob/main/cloudmesh/bar/command/bar.py
> prints the parameter as dict
> {'a': 'b', 'c': 'd'}
Metadata
Release files for cloudmesh-bumpversion 5.0.29
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 |
|---|---|---|---|---|
| cloudmesh-bumpversion-5.0.29.tar.gz | 9.6 kB | Without provenance | Details for cloudmesh-bumpversion-5.0.29.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cloudmesh_bumpversion-5.0.29-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for cloudmesh_bumpversion-5.0.29-py2.py3-none-any.whl |
Total release size: 17.6 kB
Release files / cloudmesh-bumpversion-5.0.29.tar.gz
| Download URL | cloudmesh-bumpversion-5.0.29.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e35b72dc34c050ac36b2d69648ebc6438ae57ffc9334f3b4d4e78247db9c01d0
|
|
BLAKE2b-256 checksum How to use checksums |
bd20b9e904cf9a6f2154b8d410b999e7e4254f7a6600f72deef10ca3862d4cdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / cloudmesh_bumpversion-5.0.29-py2.py3-none-any.whl
| Download URL | cloudmesh_bumpversion-5.0.29-py2.py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
e8ad50acf6848e4167b74910be441e12a18954e55a5fe2aca2ae708e638da273
|
|
BLAKE2b-256 checksum How to use checksums |
e817a7339d4d5ef2f94d0abc7e189cd02ac7d9e691ebd395fccb9118c342592a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for cloudmesh-bumpversion 5.0.29
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.