Update pulp-glue requirement from <0.30,>=0.18.0 to >=0.18.0,<0.31

[dependabot]

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

Changelog

Sourced from pulp-glue's changelog.

0.30.0 (2025-01-15) {: #0.30.0 }

Features {: #0.30.0-feature }

• Added --file-url option to file, python and rpm content create commands. #file_url

Bugfixes {: #0.30.0-bugfix }

• Fixed OAuth2 not using the provided CA bundle. #1096
• Fixed the error message for pulp config edit to properly hint at pulp config create.
• Fixes from_config call that messed up the headers attribute.

Improved Documentation {: #0.30.0-doc }

• Fixed formatting and removed a confusing part of advanced features.

Deprecations and Removals {: #0.30.0-removal }

• Drop support for the now unsupported Python version 3.8.

Misc {: #0.30.0-misc }

• Replaced python-toml dependency with a delicate combination of tomllib, tomli and tomli-w. #1084
• Declare compatibility with Python 3.13.

Pulp GLUE {: #0.30.0-pulp-glue }

Deprecations and Removals {: #0.30.0-pulp-glue-removal }

• Drop support for the now unsupported Python version 3.8.

Misc {: #0.30.0-pulp-glue-misc }

• Declare compatibility with Python 3.13.

---

... (truncated)

Commits

• 710e125 Release 0.30.0
• 716f8b5 Add querystrings to debug output
• 178b092 [PIP] Update pygments requirement from <2.19,>=2.17.2 to >=2.17.2,<2.20
• ac5f7bf Ignore a mypy complaint about a fixture redefinition
• 061072b Fix an unreported typing issue
• ef65293 [PIP] Bump mypy from 1.13.0 to 1.14.1
• f693751 Adjust test matrix
• b45c0a9 [PIP] Update pytest-subtests requirement
• 6d660fb Rafactor extract params into a private method
• 239a938 Refactor parse_response
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[Odilhao]

Can get this backported to 3.63 @mdellweg ?

[patchback]

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

❌ Failed to cleanly apply 3e8b765 on top of patchback/backports/3.63/3e8b765525916406304279f2b071220c62a2e02b/pr-6211

Backporting merged PR #6211 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/3e8b765525916406304279f2b071220c62a2e02b/pr-6211 upstream/3.63

4. Now, cherry-pick PR Update pulp-glue requirement from <0.30,>=0.18.0 to >=0.18.0,<0.31 #6211 contents into that branch:

   $ git cherry-pick -x 3e8b765525916406304279f2b071220c62a2e02b

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

   $ git cherry-pick -m1 -x 3e8b765525916406304279f2b071220c62a2e02b

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.30,>=0.18.0 to >=0.18.0,<0.31 #6211 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.63/3e8b765525916406304279f2b071220c62a2e02b/pr-6211

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.69: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.69/3e8b765525916406304279f2b071220c62a2e02b/pr-6211

Backported as #6215

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

[mdellweg]

@Odilhao #6216