Releases: ansible-community/antsibull-build
Releases · ansible-community/antsibull-build
0.55.0
Release Summary
Release with new features, other improvements, a new build system, and a deprecation
Major Changes
- Change pyproject build backend from
poetry-core
tohatchling
.pip install antsibull
works exactly the same as before, but some users may be affected depending on how they build/install the project (#490).
Minor Changes
- Add a
-I
/--ignore
and a--ignores-file
flag to theantsibull-build validate-tags
andantsibull-build validate-tags-file
subcommands to ignore errors for certain collections (#491). - Make compatible with deprecations issued by newer setuptools releases (#433, #502).
- Use the pypa
build
tool to build wheels and source distributions for ansible in an isolated environment. This replaces direct calls topython setup.py bdist_wheel
andpython setup.py sdist
which are deprecated (#492).
Deprecated Features
- The
multiple
andcollection
subcommands are deprecated and will be removed soon. They were never used to our knowledge except in the exploratory phase before the first Ansible 2.10 releases, have no test coverage, and might not even work at all. If you are actively using them and are interested in keeping them, please create an issue in the antsibull repository as soon as possible (#505).
0.54.0
Release Summary
New release with features, bugfixes, and breaking changes.
Breaking Changes / Porting Guide
- Drop support for Python 3.8 (#465).
Removed Features (previously deprecated)
- Removed the
antsibull-lint
command line utility. It had no functionality anymore for some time now (#466).
Bugfixes
0.53.0
Release Summary
Feature and bugfix release.
Minor Changes
- Add
--tags-file
option to thesingle
,rebuild-single
, andprepare
subcommands. This allows including a collection git tags data file in ansible-build-data and the ansible sdist (#476). - Add
pyproject.toml
to ansible sdist to use thesetuptools.build_meta
PEP 517 <https://peps.python.org/pep-0517/>
__ backend. Tools that still callsetup.py
directly will work the same as they did before (#471). - Bump minimum
antsibull-core
requirement to 1.5.0. It contains changes that are needed for the new--tags-file
option (#476). - There have been internal refactorings to simplify typing (#469).
Bugfixes
0.52.0
Release Summary
Major feature and bugfix release with breaking changes.
Minor Changes
- Add a
validate-tags
subcommand to ensure that collection versions in an Ansible release are tagged in collections' respective git repositories (#456). - Make compatible with antsibull-core 2.x.y (#463).
Breaking Changes / Porting Guide
- Drops support for Python 3.6 an 3.7 (#458, #460).
- The antsibull-docs dependency has been removed (#451).
Removed Features (previously deprecated)
- The deprecated
antsibull-lint
subcommands have been removed. Useantsibull-changelog lint-changelog-yaml
orantsibull-docs lint-collection-docs
depending on your use-case (#451). - The deprecated
build-collection
subcommand ofantsibull-build
has been removed. Usecollection
instead (#451). - The deprecated
build-multiple
subcommand ofantsibull-build
has been removed. Usemultiple
instead (#451). - The deprecated
build-single
subcommand ofantsibull-build
has been removed. Usesingle
instead (#451). - The deprecated
new-acd
subcommand ofantsibull-build
has been removed. Usenew-ansible
instead (#451).
0.51.2
Release Summary
Bugfix release. The next minor release will no longer support Python 3.6 and 3.7.
Bugfixes
- Add
--collection-dir
to theantsibull-build
collection
andbuild-collection
subcommands. Previously, the--collection-dir
option was added to the wrong CLI argument parser and not exposed to users. (#461). - Use compatibility code instead of trying to run
asyncio.run
directly, which will fail with Python 3.6 (#459).
0.51.1
0.51.0
0.50.0
Release Summary
Feature and bugfix release.
Minor Changes
- Added galaxy
requirements.yml
file asbuild-release
role depends oncommunity.general
collection (#432) - Define minimal Python requirement for Ansible X depending on X, under the assumption that ansible-core's Python requirement is increased by one version every two ansible-core major releases, and that every Ansible major release corresponds to an ansible-core major release from Ansible 5 on (#448).
- The
build-release
role fails to execute when./build/antsibull-build-data
doesn't exist and when theantsibull_data_reset
variable is set tofalse
(#442). - When building Ansible 6.3.0 or newer, fail on collection dependency validations (ansible-community/community-topics#94, #440).
Bugfixes
0.49.0
Release Summary
Bugfix and feature release containing breaking changes in the release role.
Minor Changes
- Allow to copy the files used to create the source distribution and wheels to a new directory during
antsibull-build rebuild-single
(#435). - Perform minor refactoring of the
build-release
role, mostly concerningtasks/tests.yml
. This reduces use ofshell
andset_fact
, makes the role more robust, and replaces short names with FQCNs (#432). - Show warnings emitted by building the source distribution and/or wheels (#435).
- The files in the source repository now follow the REUSE Specification. The only exceptions are changelog fragments in
changelogs/fragments/
(#437).
Breaking Changes / Porting Guide
- The
build-release
role now depends on thecommunity.general
collection (#432).
Bugfixes
- Fix typo in generated MANIFEST.in to list the existing file
README.rst
instead of the non-existing fileREADME
(#435). - When preparing a new Ansible release, only use pre-releases for ansible-core when the Ansible release itself is an alpha pre-release. This encodes that the first beta release of a new major Ansible release coincides with the ansible-core GA (#436).
0.48.0
Release Summary
Bugfix and feature release containing some breaking changes in the release role.
Minor Changes
- In the release role, automatically set
antsibull_build_file
andantsibull_data_dir
based onantsibull_ansible_version
(#430). - The release role has now an argument spec (#430).
Breaking Changes / Porting Guide
- In the release role,
antsibull_ansible_version
andantsibull_ansible_git_version
must now always be specified (#430).
Bugfixes
- When preparing a new Ansible release, bump the ansible-core version to the latest bugfix version (#430).