Repository navigation
chore: release 1.19.1 - #146
Merged
Merged
Conversation
Owner
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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
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.
Patch release carrying #145 (the sparse solver path dropped negative modes for an indefinite
K), plus the follow-ups from renaming the default branch tomainand a broken docs badge.Three commits:
chore: point branch references at main after the rename from master. The default branch was renamed with GitHub's rename feature today, anddevwas created from it. This updates the CI trigger (pushonmainanddev), the release-readiness workflow default, the release checklist, the docs prose, the issue template, and everyblob/master/tree/masterlink (VALIDATION.md alone had 171). GitHub redirects the old links, but they should not depend on that. CHANGELOG history is left as written.docs: serve the docs badge through shields.io. The README badge pointed atreadthedocs.org/projects/pybmodes/badge/, which now 307-redirects toapp.readthedocs.organd rate-limits GitHub's image proxy: fetching it through camo returns502 Invalid upstream response (429), so it rendered as a broken image. The docs build itself is passing. shields.io queries the RTD API and caches the result, and it is what the conda-forge and Python badges already use. The README is also the PyPI description, so this fixes the badge there too.chore: bump version to 1.19.1, promote CHANGELOG. Onlypyproject.toml, the__init__fallback,CITATION.cffandCHANGELOG.md.Pre-tag verification
--strict)bmodesarchive-only, pre-existing), 0 FAILAfter merge, the Validation (external data) workflow runs on the merge commit on
mainbefore thev1.19.1tag goes up.