The Zuul team is pleased to announce the release of Zuul 8.0.0.
Download it from PyPI: https://pypi.org/project/zuul
Find container images at: https://hub.docker.com/u/zuul
The release notes, included below, are also available in the documentation with hyperlink references:
https://zuul-ci.org/docs/zuul/8.0.0/releasenotes.html
New Features ============
* Read-level access to tenants or the tenant list may now be restricted to authorized users using the tenant.access-rules and api-root.access-rules attributes.
* The rebase merge-mode is now supported for GitHub.
Upgrade Notes =============
* Support for Ansible version 5 has been removed. Migrate any existing jobs which rely on this version to Ansible version 6 before upgrading.
* In preparation for expanded access control features in the web interface, and REST API, the admin-rule tenant configuration object has been renamed to authorization-rule. When applied to a tenant, the tenant attribute is still admin-rules since it determines admin access to that tenant. This change will allow similar rules to be applied to non-admin level access in the future.
Tenant configs should now follow this example:
- authorization-rule: name: example-rule - tenant: name: example-tenant admin-rules: - example-rule
The old form is still permitted for backwards compatability, but will be removed in a later version of Zuul.
* The default merge mode used by Zuul for preparing git repos was previously merge-resolve in all cases, but is now merge for all drivers except Gerrit, where merge-resolve is still the default. This makes the merge operations performed by Zuul more closely match the operations that will be performed by the code review systems.
Bug Fixes =========
* The use of implied branch matchers in jobs where override-checkout was specified could cause some jobs to include unintended variants. Specifically: job variants with implied branch matchers on branches which are substring matches of a branch specified in the override-checkout job attribute may have been used when not intended.
* This has been corrected so that the same job variant matching process happens whether the change’s branch or the branch specified by override-checkout is used.