Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40

[dependabot]

Updates the requirements on pulp-glue to permit the latest version.

Changelog

Sourced from pulp-glue's changelog.

0.39.0 (2026-04-08) {: #0.39.0 }

Features {: #0.39.0-feature }

• Added a prn argument to pulp show. #1236
• Added --version option to pulp python distribution for serving content from a specific repository version. #1324
• Added repair-metadata command to pulp python repository for repairing package metadata. #1340
• Added missing REST API filters to content list commands across all plugins and grouped common content filters (repository_version, repository_version_added, repository_version_removed) into reusable content_filter_options.

Bugfixes {: #0.39.0-bugfix }

• Fixed warnings about parameters being used multiple times. #1315
• Prevent picking up ~/.netrc logins.

Pulp GLUE {: #0.39.0-pulp-glue }

Features {: #0.39.0-pulp-glue-feature }

• Added resolve_prn to the PulpContext as a factory for PulpEntityContext objects. #1236
• Added repository version logic to PulpPythonDistributionContext for pulp_python>=3.21.0. #1324
• Added repair_metadata method to PulpPythonRepositoryContext for pulp_python>=3.26.0. #1340

Bugfixes {: #0.39.0-pulp-glue-bugfix }

• Fixed PulpEntityContext.update method to correctly pass partial=True to preprocess_entity.

---

0.38.2 (2026-03-04) {: #0.38.2 }

No significant changes.

Pulp GLUE {: #0.38.2-pulp-glue }

... (truncated)

Commits

• 03d1879 Release 0.39.0
• 8767d81 Update cookiecutter
• 3accfde Update cookiecutter
• bc44820 Fix duplicate options warnings
• 5d03ee7 Use pydantic in openapi spec
• b2bd35b Add some pydantic models for validation
• f8ef5fe [PIP] Update requests requirement in /pulp-glue
• 27673d3 [PIP] Update mypy requirement from ~=1.19.1 to ~=1.20.0
• 257b7da [PIP] Update pygments requirement from <2.20,>=2.17.2 to >=2.17.2,<2.21
• f74f12d Update cookiecutter
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[patchback]

Backport to 3.63: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 03ecea3 on top of patchback/backports/3.63/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backporting merged PR #7570 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.63/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570 upstream/3.63

4. Now, cherry-pick PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 contents into that branch:

   $ git cherry-pick -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

   If it'll yell at you with something like fatal: Commit 03ecea30d7c39d7670ab43d26e3eba5c71b36bae is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.63/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.49: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 03ecea3 on top of patchback/backports/3.49/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backporting merged PR #7570 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.49/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570 upstream/3.49

4. Now, cherry-pick PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 contents into that branch:

   $ git cherry-pick -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

   If it'll yell at you with something like fatal: Commit 03ecea30d7c39d7670ab43d26e3eba5c71b36bae is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.49/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.85: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 03ecea3 on top of patchback/backports/3.85/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backporting merged PR #7570 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.85/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570 upstream/3.85

4. Now, cherry-pick PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 contents into that branch:

   $ git cherry-pick -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

   If it'll yell at you with something like fatal: Commit 03ecea30d7c39d7670ab43d26e3eba5c71b36bae is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.85/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.73: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 03ecea3 on top of patchback/backports/3.73/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backporting merged PR #7570 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulpcore.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.73/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570 upstream/3.73

4. Now, cherry-pick PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 contents into that branch:

   $ git cherry-pick -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

   If it'll yell at you with something like fatal: Commit 03ecea30d7c39d7670ab43d26e3eba5c71b36bae is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 03ecea30d7c39d7670ab43d26e3eba5c71b36bae

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update pulp-glue requirement from <0.39,>=0.30.0 to >=0.30.0,<0.40 #7570 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.73/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.105: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.105/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backported as #7572

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.107: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.107/03ecea30d7c39d7670ab43d26e3eba5c71b36bae/pr-7570

Backported as #7573

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.