Correction, latest pulp_container release 1.3.0 is compatible with pulpcore 3.3.0
-------- Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Apr 23, 2020 at 6:15 PM Ina Panova <ipan...@redhat.com> wrote: > pulp_container 1.3.0 is released with the set of new features and > bugfixes. It is also compatible with pulpcore 3.1. > > https://pulp-container.readthedocs.io/en/latest/changes.html#id1 > https://pypi.org/project/pulp-container/1.3.0/ > -------- > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > > On Thu, Apr 16, 2020 at 5:34 PM Mike DePaulo <mikedep...@redhat.com> > wrote: > >> Here is another highlight for pulp_installer 3.3.0 [1]: >> * Added support for RHEL8 & CentOS 8 [2] >> >> [1] https://github.com/pulp/pulp_installer/releases/tag/3.3.0 >> [2] https://pulp.plan.io/issues/6259 >> >> On Thu, Apr 16, 2020 at 10:04 AM Tatiana Tereshchenko < >> ttere...@redhat.com> wrote: >> >>> Pulpcore 3.3.0 [0] and pulp_file 0.3.0 [1] have been released. For a >>> list of all changes, please check the changelogs for pulpcore [2] and >>> pulp_file [3]. Here are some highlights: >>> * Import/export of repository versions (tech preview) >>> * Repository version repairing (tech preview) [4] >>> * S3 is now fully supported and no longer a tech preview >>> * Various bugfixes and performance improvements >>> >>> The only backwards incompatible change [5] is: >>> * Exporting now requires ALLOWED_EXPORT_PATHS setting. >>> >>> # Installation and Upgrade >>> >>> Users should use the 3.3.0 release of pulp_installer (previously known >>> as ansible-pulp) [6] to install or upgrade their installations. This >>> version of the installer will check compatibility of all installed plugins >>> with pulpcore 3.3. The installer will abort if any plugin is incompatible. >>> >>> # Plugin API >>> >>> Plugin writers can see the plugin API changelog here [7]. >>> There were a couple backwards incompatible changes [8]: >>> * One is about Exporter (you are not affected unless you have already >>> started integrating with it). >>> * The other one makes it the responsibility of a plugin to check the >>> duplicated content in a repository version. Pulpcore provides validation >>> methods to do so. See the pulp_file example [9]. >>> >>> And in keeping with the recommended strategy to pin plugins to a 3.y >>> version of pulpcore, plugins should release compatibility releases with 3.3 >>> as soon as they can. We recommend using "pulpcore>=3.3,<3.4". >>> >>> [0] https://pypi.org/project/pulpcore/3.3.0/ >>> [1] https://pypi.org/project/pulp-file/0.3.0/ >>> [2] https://docs.pulpproject.org/changes.html#id1 >>> [3] https://pulp-file.readthedocs.io/en/0.3.0/changes.html#id1 >>> [4] >>> https://docs.pulpproject.org/workflows/repairing-repository-versions.html >>> [5] https://docs.pulpproject.org/changes.html#deprecations-and-removals >>> [6] https://github.com/pulp/pulp_installer/releases/tag/3.3.0 >>> [7] https://docs.pulpproject.org/en/3.3.0/changes.html#plugin-api >>> [8] https://docs.pulpproject.org/changes.html#id50 >>> [9] >>> https://github.com/pulp/pulp_file/commit/dc6acb9d60a1d3aa61ff4def99cc12ddd9981076 >>> _______________________________________________ >>> 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 > >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list