antsibull-nox -- Antsibull Nox Helper
A nox helper for Ansible collections. Please check out the documentation for more information.
antsibull-nox is covered by the Ansible Code of Conduct.
Community
Need help or want to discuss the project? See our Community guide to learn how to join the conversation!
Installation
It can be installed with pip:
pip install antsibull-nox
Versioning and compatibility
From version 1.0.0 on, antsibull-nox sticks to semantic versioning and aims at providing no backwards compatibility breaking changes to the documented API during a major release cycle. We might make exceptions from this in case of security fixes for vulnerabilities that are severe enough.
Interfaces and functions that are not documented in the API reference are exempt from this and might break even in bugfix releases!
Development
Install and run nox to run all tests. That's it for simple contributions!
nox will create virtual environments in .nox inside the checked out project
and install the requirements needed to run the tests there.
antsibull-nox depends on the sister antsibull-changelog, antsibull-docutils, and antsibull-fileutils projects.
By default, nox will install development versions of this projects from Github.
If you're hacking on antsibull-changelog, antsibull-docutils, and/or antsibull-fileutils alongside antsibull-nox,
nox will automatically install these projects from ../antsibull-changelog, ../antsibull-docutils, and ../antsibull-fileutils
when running tests if those paths exist.
You can change this behavior through the OTHER_ANTSIBULL_MODE env var:
OTHER_ANTSIBULL_MODE=auto— the default behavior described aboveOTHER_ANTSIBULL_MODE=local— install the projects from../antsibull-changelog,../antsibull-docutils, and../antsibull-fileutils. Fail if that path doesn't exist.OTHER_ANTSIBULL_MODE=git— install the projects from the Github main branchOTHER_ANTSIBULL_MODE=pypi— install the latest versions from PyPI
To run specific tests:
nox -e testto only run unit tests;nox -e lintto run all linters and formatters at once;nox -e formattersto runisortandblack;nox -e codeqato runflake8,pylint,reuse lint, andantsibull-changelog lint;nox -e typingto runmypy.
Creating a new release:
- Run
nox -e bump -- <version> <release_summary_message>. This:- Bumps the package version in
src/antsibull_nox/__init__.py. - Creates
changelogs/fragments/<version>.ymlwith arelease_summarysection. - Runs
antsibull-changelog releaseand adds the changed files to git. - Commits with message
Release <version>.and runsgit tag -a -m 'antsibull-nox <version>' <version>. - Runs
hatch build --clean.
- Bumps the package version in
- Run
git pushto the appropriate remotes. - Once CI passes on GitHub, run
nox -e publish. This:- Runs
hatch publish; - Bumps the version to
<version>.post0; - Adds the changed file to git and run
git commit -m 'Post-release version bump.';
- Runs
- Run
git push --follow-tagsto the appropriate remotes and create a GitHub release.
License
Unless otherwise noted in the code, it is licensed under the terms of the GNU General Public License v3 or, at your option, later. See LICENSES/GPL-3.0-or-later.txt for a copy of the license.
The repository follows the REUSE Specification for declaring copyright and licensing information.
Metadata
Release files for antsibull-nox 1.10.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 |
|---|---|---|---|---|
| antsibull_nox-1.10.0.tar.gz | 287.6 kB | Without provenance | Details for antsibull_nox-1.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antsibull_nox-1.10.0-py3-none-any.whl | Python 3 | none | any | Details for antsibull_nox-1.10.0-py3-none-any.whl |
Total release size: 505.7 kB
Release files / antsibull_nox-1.10.0.tar.gz
| Download URL | antsibull_nox-1.10.0.tar.gz |
|---|---|
| Size | 287.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8483275210865771696372ecdce90025c90f93c095fe6f897b9ad9ce88803b91
|
|
BLAKE2b-256 checksum How to use checksums |
39d5befdc81b5b4d3cf58633e51cad9712603e33a18d37c4fca4aa0fd511dbfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.1 {"ci":null,"cpu":"x86_64","distro":{"id":"n/a","libc":{"lib":"glibc","version":"2.44"},"name":"Arch Linux","version":"rolling"},"implementation":{"name":"CPython","version":"3.14.8"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 3.6.5 29 Sep 2026","python":"3.14.8","system":{"name":"Linux","release":"7.2.7-arch1-1"}} HTTPX2/2.16.0
|
Release files / antsibull_nox-1.10.0-py3-none-any.whl
| Download URL | antsibull_nox-1.10.0-py3-none-any.whl |
|---|---|
| Size | 218.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f09059aafff237b8d6f9511a9562925e91ec946cdb2f21805419f5d0be10ae7
|
|
BLAKE2b-256 checksum How to use checksums |
a9e7f0c5b10c9f7eba435fbe149fa286770dd1c5a69883b97b25bd919fa483e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.18.1 {"ci":null,"cpu":"x86_64","distro":{"id":"n/a","libc":{"lib":"glibc","version":"2.44"},"name":"Arch Linux","version":"rolling"},"implementation":{"name":"CPython","version":"3.14.8"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 3.6.5 29 Sep 2026","python":"3.14.8","system":{"name":"Linux","release":"7.2.7-arch1-1"}} HTTPX2/2.16.0
|
Security for antsibull-nox 1.10.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.
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.