Antsibull

Latest version: v0.63.1

Safety actively analyzes 629639 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 21

0.45.0

=======

Release Summary
---------------

New feature release with one breaking change to the ``build-release`` role.

Minor Changes
-------------

- Add ``antsibull-build`` subcommand ``validate-deps`` which validates dependencies for an ``ansible_collections`` tree (https://github.com/ansible-community/antsibull/pull/416).
- Check collection dependencies during ``antsibull-build rebuild-single`` and warn about errors (https://github.com/ansible-community/antsibull/pull/416).
- In the ``build-release`` role, stop shipping a separate ``roles/build-release/files/deps-to-galaxy.py`` script and use the new galaxy-requirements.yaml style file created during release preparation (https://github.com/ansible-community/antsibull/pull/417).
- Update Ansible's ``README.rst`` to focus on Ansible package details (https://github.com/ansible-community/antsibull/pull/415).
- When preparing a new Ansible release with ``antsibull-build prepare`` or ``antsibull-build single``, create a galaxy-requirements.yaml style file next to the dependencies file (https://github.com/ansible-community/antsibull/pull/417).

Breaking Changes / Porting Guide
--------------------------------

- The ``build-release`` role no longer uses poetry to run antsibull, but assumes that antsibull is installed. To revert to the old behavior, set the Ansible variable ``antsibull_build_command`` to ``poetry run antsibull`` (https://github.com/ansible-community/antsibull/pull/420).

0.44.0

=======

Release Summary
---------------

Split up antsibull into multiple PyPi packages (``antsibull-core``, ``antsibull-docs``, and ``antsibull``). **Note** that upgrading is a bit more complicated due to the way ``pip`` works! See below for details.

Major Changes
-------------

- The ``antsibull`` package now depends on ``antsibull-core`` and ``antsibull-docs``, and most code was moved to these two packages. The ``antsibull-docs`` CLI tool is now part of the ``antsibull-docs`` package as well. The behavior of the new version should be identical to the previous version (https://github.com/ansible-community/antsibull/pull/414).

Deprecated Features
-------------------

- The antsibull-lint command is deprecated. Use ``antsibull-changelog lint-changelog-yaml`` instead of ``antsibull-lint changelog-yaml``, and use ``antsibull-docs lint-collection-docs`` instead of ``antsibull-lint collection-docs`` (https://github.com/ansible-community/antsibull/pull/412, https://github.com/ansible-community/antsibull/issues/410).

Known Issues
------------

- When upgrading from antsibull < 0.44.0 to antsibull 0.44.0+, it could happen that the ``antsibull-docs`` binary is removed due to how pip works. To make sure the ``antsibull-docs`` binary is present, either first uninstall (``pip uninstall antsibull``) before installing the latest antsibull version, or re-install ``antsibull-docs`` once the installation finished (``pip install --force-reinstall antsibull-docs``) (https://github.com/ansible-community/antsibull/pull/414).

0.43.0

=======

Release Summary
---------------

Feature release.

Minor Changes
-------------

- Add ``lint-collection-docs`` subcommand to ``antsibull-docs``. It behaves identical to ``antsibull-lint collection-docs`` (https://github.com/ansible-community/antsibull/pull/411, https://github.com/ansible-community/antsibull/issues/410).
- Support ``MANIFEST.json`` and not only ``galaxy.yml`` for ``antsibull-docs lint-collection-docs`` and ``antsibull-lint collection-docs`` (https://github.com/ansible-community/antsibull/pull/411).

Bugfixes
--------

- Prevent crashing when non-strings are found for certain pathnames for ``antsibull-docs lint-collection-docs`` and ``antsibull-lint collection-docs`` (https://github.com/ansible-community/antsibull/pull/411).

0.42.1

=======

Release Summary
---------------

Bugfix release.

Bugfixes
--------

- antsibull-docs sphinx-init - the ``--fail-on-error`` option resulted in an invalid ``build.sh`` (https://github.com/ansible-community/antsibull/pull/409).

0.42.0

=======

Release Summary
---------------

Major feature release preparing for Ansible 6. Also adds support for the new collection links file, and improves the attributes tables.

Major Changes
-------------

- Allow collections to specify extra links (https://github.com/ansible-community/antsibull/pull/355).
- Building Ansible 6+ now builds wheels next to the source tarball (https://github.com/ansible-community/antsibull/pull/394).
- From Ansible 6 on, improve ``setup.py`` to exclude unnecessary files in the Python distribution (https://github.com/ansible-community/antsibull/pull/342).
- Remove Ansible 2.9 / ansible-base 2.10 checks from ``setup.py`` for Ansible 6 so that we can finally ship wheels. This change is only active for Ansible 6 (https://github.com/ansible-community/antsibull/pull/394).

Minor Changes
-------------

- Add a new docs parsing backend ``ansible-core-2.13``, which supports ansible-core 2.13+ (https://github.com/ansible-community/antsibull/pull/401).
- Add an autodetection ``auto`` for the docs parsing backend to select the fastest supported backend. This is the new default (https://github.com/ansible-community/antsibull/pull/401).
- Add option ``--no-semantic-versioning`` to ``antsibull-lint changelog-yaml`` command (https://github.com/ansible-community/antsibull/pull/405).
- Change more references to ansible-base to ansible-core in the code (https://github.com/ansible-community/antsibull/pull/398).
- If the role is used to build a non-alpha or first beta version and the bulid file does not exist, it is created instead of later failing because it does not exist (https://github.com/ansible-community/antsibull/pull/408).
- Mention the ``ansible-core`` major version in the Ansible porting guide (https://github.com/ansible-community/antsibull/pull/397).
- Redo attributes table using the same structure as the options and return value table. This improves its look and adds a linking mechanism (https://github.com/ansible-community/antsibull/pull/401).

Bugfixes
--------

- Fix ansible-core version parsing for ``ansible-doc`` docs parsing backend (https://github.com/ansible-community/antsibull/pull/401).
- Fix filename of mentioned ansible-core porting guide in Ansible's porting guide introductionary comment (https://github.com/ansible-community/antsibull/pull/398).
- antsibull-docs will no longer traceback when it tries to process plugins not found in its own constant but are available in ansible-core (https://github.com/ansible-community/antsibull/pull/404).

0.41.0

=======

Release Summary
---------------

Feature and bugfix release.

Minor Changes
-------------

- Add ``--fail-on-error`` to all antsibull-docs subcommands for usage in CI (https://github.com/ansible-community/antsibull/pull/393).
- Allow to select a different Sphinx theme for ``antsibull-docs sphinx-init`` with the new ``--sphinx-theme`` option (https://github.com/ansible-community/antsibull/pull/392).
- Fully implement ``antsibull-docs collection``. So far ``--current`` was required (https://github.com/ansible-community/antsibull/pull/383).
- Mention the plugin type more prominently in the documentation (https://github.com/ansible-community/antsibull/pull/364).
- Remove email addresses and ``(!UNKNOWN)`` from plugin and role author names (https://github.com/ansible-community/antsibull/pull/389).
- Support new ``keyword`` field in plugin documentations (https://github.com/ansible-community/antsibull/pull/329).
- The ``conf.py`` generated by ``antsibull-docs sphinx-init`` will be set to try resolving intersphinx references to Ansible's ``devel`` docs instead of a concrete Ansible version (https://github.com/ansible-community/antsibull/pull/391).

Bugfixes
--------

- If plugin parsing fails for ``antsibull-docs plugin``, handle this more gracefully (https://github.com/ansible-community/antsibull/pull/393).
- Improve error message when plugin specified for ``antsibull-docs plugin`` cannot be found (https://github.com/ansible-community/antsibull/pull/383).
- When using ``--use-html-blobs``, malformed HTML was generated for parameter aliases (https://github.com/ansible-community/antsibull/pull/388).

Page 12 of 21

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.