Repository navigation
chore(deps-dev): update pydata-sphinx-theme requirement from <0.22.0,>=0.16.1 to >=0.16.1,<0.24.0 - #162
Merged
gsvgit merged 1 commit intoOct 14, 2026
Conversation
Updates the requirements on [pydata-sphinx-theme](https://github.com/pydata/pydata-sphinx-theme) to permit the latest version. - [Release notes](https://github.com/pydata/pydata-sphinx-theme/releases) - [Changelog](https://github.com/pydata/pydata-sphinx-theme/blob/main/RELEASE.md) - [Commits](pydata/pydata-sphinx-theme@v0.16.1...v0.23.0) --- updated-dependencies: - dependency-name: pydata-sphinx-theme dependency-version: 0.23.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
gsvgit
approved these changes
Oct 14, 2026
dependabot
Bot
deleted the
dependabot/pip/dev/pydata-sphinx-theme-gte-0.16.1-and-lt-0.24.0
branch
October 14, 2026 06:41
gsvgit
added a commit
that referenced
this pull request
Oct 14, 2026
The S1 commit picked up a locally regenerated uv.lock (the pre-existing dependabot #162 specifier drift plus a lockfile revision bump from a newer local uv). That change is out of scope for this task; restore the lock to the dev state.
gsvgit
added a commit
that referenced
this pull request
Oct 14, 2026
Bump the version to 6.1.0 and promote the [Unreleased] changelog section to [6.1.0] - 2026-10-14. The release is minor: everything since 6.0.0 is additive (the flpq-check-archive console command, the flpq_data.tools and flpq_data.dataset.s3 modules, utils/add_reachable_pairs.py) with no changes to the existing public API, and the dataset prefix stays at 6.0.0. uv.lock is re-locked in the same commit: it must track the new package version for CI's 'uv sync --frozen', and it also picks up the pydata-sphinx-theme specifier that #162 changed in pyproject.toml without re-locking, which left the lockfile stale.
gsvgit
pushed a commit
that referenced
this pull request
Oct 15, 2026
Updates the requirements on [pydata-sphinx-theme](https://github.com/pydata/pydata-sphinx-theme) to permit the latest version. - [Release notes](https://github.com/pydata/pydata-sphinx-theme/releases) - [Changelog](https://github.com/pydata/pydata-sphinx-theme/blob/main/RELEASE.md) - [Commits](pydata/pydata-sphinx-theme@v0.16.1...v0.23.0) --- updated-dependencies: - dependency-name: pydata-sphinx-theme dependency-version: 0.23.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
gsvgit
added a commit
that referenced
this pull request
Oct 15, 2026
The S1 commit picked up a locally regenerated uv.lock (the pre-existing dependabot #162 specifier drift plus a lockfile revision bump from a newer local uv). That change is out of scope for this task; restore the lock to the dev state.
gsvgit
added a commit
that referenced
this pull request
Oct 15, 2026
Bump the version to 6.1.0 and promote the [Unreleased] changelog section to [6.1.0] - 2026-10-14. The release is minor: everything since 6.0.0 is additive (the flpq-check-archive console command, the flpq_data.tools and flpq_data.dataset.s3 modules, utils/add_reachable_pairs.py) with no changes to the existing public API, and the dataset prefix stays at 6.0.0. uv.lock is re-locked in the same commit: it must track the new package version for CI's 'uv sync --frozen', and it also picks up the pydata-sphinx-theme specifier that #162 changed in pyproject.toml without re-locking, which left the lockfile stale.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on pydata-sphinx-theme to permit the latest version.
Release notes
Sourced from pydata-sphinx-theme's releases.
Commits
560ca12Bump 0.23.0rc0 -> 0.23.01a2a2c3Bump astral-sh/setup-uv from 10.0.1 to 10.1.0 (#2489)8a67845[pre-commit.ci] pre-commit autoupdate hooks (#2518)ea0a529Bump py-cov-action/python-coverage-comment-action from 4.3 to 4.5 (#2513)daccf13Bump 0.22.0 -> 0.23.0rc0642ca72Loosen what keys can be cached in the sidebar (#2500)c223b82Fix spacing between unnamed API return types (#2499)9cfdc3eRun npm audit; bump node version; add dep cooldown (#2508)e0a5d5cPrevent unwanted renders of PST sidebar, even if disabled in configuration (#...46a8149Post-merge review for light-dark (#2506)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)