insights-ccx-messaging
Stub for all CCX services based on Insights Core Messaging framework
Makefile targets
Available targets are:
unit_tests Run unit tests
coverage Run unit tests, display code coverage on terminal
coverage-report Run unit tests, generate code coverage as a HTML report
documentation Generate documentation for all sources
shellcheck Run shellcheck
pyformat Reformat all Python sources
help Show this help screen
Releasing a new version
The project version is derived from git tags using setuptools_scm — there is no hardcoded version file.
To create a new release:
-
Tag the desired commit on
mainwith a lightweight tag following thevMAJOR.MINOR.PATCHconvention:git tag v4.X.Y git push origin v4.X.Y
-
The CI workflow (
.github/workflows/pypi-release.yaml) will automatically build and publish to PyPI.
2 maintainers
Metadata
2 maintainers
Release files for ccx-messaging 4.6.0
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 |
|---|---|---|---|---|
| ccx_messaging-4.6.0.tar.gz | 183.3 kB | With provenance | Details for ccx_messaging-4.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ccx_messaging-4.6.0-py3-none-any.whl | Python 3 | none | any | Details for ccx_messaging-4.6.0-py3-none-any.whl |
Total release size: 240.9 kB
Release files / ccx_messaging-4.6.0.tar.gz
| Download URL | ccx_messaging-4.6.0.tar.gz |
|---|---|
| Size | 183.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68e00e56c7abd88d05ca859c5551ec2f901dd57b772f963a598b7e83f46a9301
|
|
BLAKE2b-256 checksum How to use checksums |
aeff1f91dc5ea953960470aa0fa404576aaedb66cd0c436156c32125997ce1f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / ccx_messaging-4.6.0-py3-none-any.whl
| Download URL | ccx_messaging-4.6.0-py3-none-any.whl |
|---|---|
| Size | 57.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20fa3123de713f9d7a68a27802d401aa946b6ef3e1ae96273d23695c308a3547
|
|
BLAKE2b-256 checksum How to use checksums |
828c9c711c069a283e4cdef4004f61623beb3a23ab42bfc66ead05b241ed0f94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logSecurity for ccx-messaging 4.6.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ccx_messaging-4.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logA 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.
