Pulpcore/3.55 is coming soon!

Development
#1

Dear Plugin Writers,

We are going to be releasing pulpcore 3.55.0 soon - possibly as early as 2024-06-18. This release will have backwards incompatible plugin API changes. The final list of items to be aware of:

While most plugins will not need to make any changes due to the items listed above, the version of pulpcore in the requirements.txt will need to be adjusted and a compatibility release will be required. After 3.55.0, the next backwards-incompatible plugin-API release will be pulpcore 3.70.0.

3 Likes
#2

OK folks - the release-process-gears are going to start turning for core/3.55 today, 2024-06-18.

If you are a plugin-maintainer, you will need to update your plugin’s requirements.txt to allow a pulpcore upperbounds of pulpcore<3.70.

This is especially important if your plugin is currently included in the all-in-one container!

2 Likes
#3

Can we sync up our changelog entry for pulpcore upper bound version bumps across (and within) plugins?

Suggestion: “Features: Declared compatibility against pulpcore X.Y+.”

They are currently all over the place, some examples:

  • pulp_rpm:
    • Bugfixes: Allow installation with pulpcore/3.55.
    • Features: Added pulpcore 3.40 compatibility.
    • Features: Declares (and requires at least) pulpcore/3.25 compatibility.
  • pulp_deb:
    • Features: Made the plugin compatible with pulpcore 3.55.0+.
    • Features: Made the plugin compatible with pulpcore 3.40.1+.
    • Features: Declare and require at least pulpcore/3.25 compatibility.
  • pulp_container:
    • Features: Made pulp_container compatible with pulpcore 3.40.
    • Features: Updated compatibility for pulpcore 3.25 and Django 4.2.
1 Like
#4

An argument for a formulation of “Declared compatibility against pulpcore X.Y+” (where X.Y is the current breaking change release, in case of this thread 3.55, not the next one 3.70):

Communication wise, I think a changelog entry of “Declared compatibility against pulpcore<3.70” at a point in time when pulpcore 3.55 is latest, has a lot of potential to confuse anyone not intimately acquainted with the Plugin API deprecation policy (most users). So I think something like “Declared compatibility against pulpcore 3.55+” has the following virtues:

  • While less technically accurate than pulpcore<3.70 it is still true.
  • It identifies the actual existing breaking change release that now works.
  • Via the “+” It still hints that there is a range beyond the “3.55” that we also declared compatibility against.

So I quite like this variant. That being said, I think future consistency is more important than the exact schema chosen. And to achieve consistency we presumably would need to create a GitHub workflow to “automatically bump the pulpcore compatibility ceiling”.

1 Like