Pulpcore 3.7.0[0] and pulp_file 1.3.0[1] have been released.

Details of the most important changes are available in our blog[2]. For a
full list of changes, please check the changelog for pulpcore[3] and
pulp_file[4].

Starting with pulpcore 3.7 plugins can now be compatible with both 3.y and
3.y+1, this should allow users to upgrade pulpcore more easily without
waiting for every plugin you use to release a compatibility release.

# Installation and Upgrade

Users should use the 3.7.0 release of pulp_installer[5] to install or
upgrade their installations. This version of the installer will check
compatibility of all installed plugins with pulpcore 3.7. The installer
will abort if any plugin is incompatible.

The pulp_installer collection can be installed from Ansible Galaxy with the
following command:

    ansible-galaxy collection  install --force pulp.pulp_installer

The --force flag will upgrade the collection if you had a previous version
installed.

# Plugin API

Plugin writers can see the API changes here[6].

A significant change includes the 1-cycle deprecation policy for
pulpcore.plugin which allows you to safely declare dependency on
pulpcore==3.y+1 when you declare dependency on pulpcore==3.y.

With this change, the recommended strategy is to pin plugins to a 3.y and
3.y+1 version of pulpcore. So for a compatibility release with 3.7 use:
"pulpcore>=3.7,<3.9".

# Thanks

Thank you to everyone who worked so hard to make this release possible!

[0] https://pypi.org/project/pulpcore/3.7.0/
[1] https://pypi.org/project/pulp-file/1.3.0/
[2] https://pulpproject.org/2020/09/20/pulp-3.7.0-is-generally-available/
[3] https://docs.pulpproject.org/en/3.7/changes.html#id1
[4] https://pulp-file.readthedocs.io/en/latest/changes.html#id1
[5] https://galaxy.ansible.com/pulp/pulp_installer
[6] https://docs.pulpproject.org/en/3.7/changes.html#plugin-api
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to