pulp_rpm 3.4.2 has been released. It is compatible with pulpcore 3.5. PyPI: https://pypi.org/project/pulp-rpm/3.4.2/ Changelog: https://pulp-rpm.readthedocs.io/en/3.4/changes.html#id1 Docs: https://pulp-rpm.readthedocs.io/ Python bindings: https://pypi.org/project/pulp-rpm-client/3.4.2/ Ruby bindings: https://rubygems.org/gems/pulp_rpm_client/versions/3.4.2/
A correction to previous email: > We recommend using "pulpcore>=3.5,<3.*6*". Though most plugins should > continue to be compatible with 3.4 and in those cases will need to only > update the maximum version of pulpcore. On Fri, Jul 10, 2020 at 12:08 AM Dennis Kliban <dkli...@redhat.com> wrote: > Pulpcore 3.5.0[0] and pulp_file 1.1.0[1] have been released. > > It should be noted the installer has breaking changes. Upgrades will > require updating existing playbooks. Details of these changes are available > in our blog.[2] For a full list of changes, please check the changelog for > pulpcore[3] and pulp_file[4]. > > Here are some of the highlights: > > * Added start_versions= to export to allow for arbitrary incremental > exports. > * Added GroupProgressReport to track progress in a TaskGroup. > * Provide a user agent string with all aiohttp requests by default. > > # Installation and Upgrade > > Users should use the 3.5.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.5. 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]. Some highlights: > > * Views can specify the tag name with pulp_tag_name > * Added GroupProgressReport to track progress in a TaskGroup. > * Exported the symbols serializers.SingleContentArtifactField and > files.PulpTemporaryUploadedFile. > > And in keeping with the recommended strategy to pin plugins to a 3.y > version of pulpcore, plugins should release compatibility releases with 3.5 > as soon as they can. We recommend using "pulpcore>=3.5,<3.5". Though most > plugins should continue to be compatible with 3.4 and in those cases will > need to only update the maximum version of pulpcore. > > [0] https://pypi.org/project/pulpcore/3.5.0/ > [1] https://pypi.org/project/pulp-file/1.1.0/ > [2] https://pulpproject.org/2020/07/09/pulp-3.5-installer-roles/ > [3] https://docs.pulpproject.org/en/3.5/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.5/changes.html#plugin-api > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
