MAINT post-0.14.0 release update to 0.15.0.dev0#1948
Merged
Conversation
Routine post-release maintenance following the v0.14.0 release (Step 9 of the release process). Version bump (0.14.0 -> next dev cycle), mirroring microsoft#1630: - pyrit/__init__.py: __version__ = "0.15.0.dev0" - pyproject.toml: version = "0.15.0.dev0" - frontend/package.json: "version": "0.15.0-dev.0" Docs version picker (.github/docs-versions.yml): - Point default/stable to "0.14.0" so the published v0.14.0 docs are served at the site root and under /stable/. - Add a "0.14.0" entry (ref: releases/v0.14.0) to the build matrix so the version is actually built and selectable in the picker. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ValbuenaVC
force-pushed
the
chore/post-0.14.0-bump
branch
from
4e4f885 to
7307988
Compare
romanlutz
approved these changes
Jun 5, 2026
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
2 participants
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.
Description
Routine post-release maintenance following the v0.14.0 release (Step 9 of the release process). Mirrors the previous post-release bump in #1630.
Dev version bump (0.14.0 → next dev cycle):
pyrit/__init__.py:__version__ = "0.15.0.dev0"pyproject.toml:version = "0.15.0.dev0"frontend/package.json:"version": "0.15.0-dev.0"Docs version picker (
.github/docs-versions.yml):default/stableto"0.14.0"so the published v0.14.0 docs are served at the site root and under/stable/."0.14.0"entry (ref: releases/v0.14.0) to the build matrix so the version is actually built and selectable in the picker.No functional code changes.
Tests and Documentation
No tests required — version-string and docs-config changes only. The
releases/v0.14.0ref referenced by the new docs-picker entry exists onorigin, so the docs build matrix can resolve it. JupyText was not run (no notebook or code-sample changes).