chore(deps): bump the ci-dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the ci-dependencies group with 2 updates in the / directory: readmeio/rdme and pypa/gh-action-pypi-publish.

Updates readmeio/rdme from 8.6.6 to 10.0.0

Release notes

Sourced from readmeio/rdme's releases.

v10.0.0

10.0.0 (2024-12-13)

[!IMPORTANT] rdme@10 is the first official release that supports ReadMe Refactored. If your ReadMe project is not using ReadMe Refactored, you'll want to use rdme@9. More info can be found in our migration guide.

• feat!: v10 release (#1113) (f260a00)

BREAKING CHANGES

• categories, custompages, docs and versions have now been removed. Please use a bidirectional syncing workflow instead. Read more in our migration guide.
• rdme openapi has been replaced by rdme openapi upload. Read more in our migration guide.

v10.0.0-next.1

10.0.0-next.1 (2024-12-12)

• feat!: v10 release (#1113) (f260a00)

BREAKING CHANGES

• categories, custompages, docs and versions have now been removed. Please use a bidirectional syncing workflow instead. Read more in our migration guide.
• rdme openapi has been replaced by rdme openapi upload. Read more in our migration guide.

v9.0.5

9.0.5 (2024-12-12)

Bug Fixes

... (truncated)

Changelog

Sourced from readmeio/rdme's changelog.

10.0.0 (2024-12-13)

• feat!: v10 release (#1113) (f260a00)

BREAKING CHANGES

• categories, custompages, docs and versions have now been removed. Please use a bidirectional syncing workflow instead. Read more in our migration guide.
• rdme openapi has been replaced by rdme openapi upload. Read more in our migration guide.

10.0.0-next.1 (2024-12-12)

• feat!: v10 release (#1113) (f260a00)

BREAKING CHANGES

• categories, custompages, docs and versions have now been removed. Please use a bidirectional syncing workflow instead. Read more in our migration guide.
• rdme openapi has been replaced by rdme openapi upload. Read more in our migration guide.

9.0.5 (2024-12-12)

Bug Fixes

• do not force push a tag called v9 (df27049)

9.0.5-next.1 (2024-12-12)

Bug Fixes

• do not force push a tag called v9 (df27049)

9.0.4 (2024-12-12)

Bug Fixes

... (truncated)

Commits

• eaa40e8 build(release): 🚀 v10.0.0 🦉
• 0388be1 chore: empty commit to trigger build
• f05d6f0 build(release): 🚀 v10.0.0-next.1 🦉
• f260a00 feat!: v10 release (#1113)
• af1a9f9 build(release): 🚀 v9.0.5 🦉
• 12cb7bd chore: empty commit to trigger build
• 1d66c2e build(release): 🚀 v9.0.5-next.1 🦉
• 68abc57 chore: empty commit to trigger build
• b6da183 Merge branch 'main' into next
• 2184427 build(release): 🚀 v9.0.4-next.5 🦉
• Additional commits viewable in compare view

Updates pypa/gh-action-pypi-publish from 1.12.2 to 1.12.3

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.12.3

✨ What's Improved

With the updates by @​woodruffw💰 and @​webknjaz💰 via #309 and #313, it is now possible to publish distribution packages that include core metadata v2.4, like those built using maturin. This is done by bumping Twine to v6.0.1 and pkginfo to v1.12.0.

📝 Docs

We've made an attempt to clarify the runtime and workflow shape that are expected to be supported for calling this action in: https://github.com/marketplace/actions/pypi-publish#Non-goals.

[!TIP] Please, let us know in the release discussion if anything still remains unclear. TL;DR always call pypi-publish once per job; don't invoke it in reusable workflows; physically move building the dists into separate jobs having restricted permissions and storing the dists as GitHub Actions artifacts; when using self-hosted runners, make sure to still use pypi-publish on a GitHub-provided infra with runs-on: ubuntu-latest, while building and testing may remain self-hosted; don't perform any other actions in the publishing job; don't call pypi-publish from composite actions.

🛠️ Internal Updates

@​br3ndonland💰 improved the container image generation automation to include Git SHA in #301. And @​woodruffw💰 added the workflow_ref context to Trusted Publishing debug logging in #305, helping us diagnose misconfigurations faster. #313 also extends the smoke test in the CI to check against the maturin-made dists. Additionally, jeepney and secretstorage transitive deps have been added to the pip constraint-based lock file, as Dependabot seems to have missed those earlier.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.12.2...v1.12.3

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​samuelcolvin💰 for nudging me to cut this release sooner and for sponsoring me via @​pydantic💰!

🔌 Shameless Plug: The other day I've made this 🦋 Bluesky 🇺🇦 FOSS Maintainers Starter Pack subscribe to read news from people like me :)

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

Commits

• 67339c7 📦 Only keep lower bounds @ input requirements
• cbd6d01 📝Fix a typo in "privileges" @ README
• 7252a9a 📝 Outline unsupported scenarios in README
• a536fa9 📌📦 Include jeepney & secretstorage pins
• 43caae4 💅📦 Split transitive dep constraints
• f371c3d Merge pull request #313 from webknjaz/maintenance/metadata-2.4
• 138a121 📌📦 Pin pkginfo to v1.12 @ runtime deps
• ff2b051 🧪 Add a Maturin-based package to CI
• 0a0a6ae 🧪 Allow CI to register multiple distributions
• e7723a4 Merge pull request #309 from trail-of-forks/ww/bumptwine
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[jmoralez]

@dependabot ignore readmeio/rdme

[dependabot]

OK, I won't notify you about readmeio/rdme again, unless you unignore it.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.