Release prep: v1.12.0 changelog and contributor docs fixes - #85
Merged
Merged
Conversation
Date the 1.12.0 notes for the release that will actually publish, and record that 1.11.0 ships inside it rather than as its own PyPI release. Refresh the README status line and stop sending outside contributors to the private design notes. Co-authored-by: Yohei Nakajima <yoheinakajima@users.noreply.github.com>
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.
Summary
Docs-only release prep for v1.12.0. No tag is created or pushed. Publishing stays with the maintainer, who tags
v1.12.0frommainafter merge. That tag push is what runs.github/workflows/publish.yml.ConcurrentWriterError,InvalidPatchOperation), single-writer andattach_storerules, detached events, and name-based pack identity, plus the 1.12.0 query-plan and optionalindexed_fieldsconfiguration.git diff --checkflagged:TRIAGE.md,.github/ISSUE_TEMPLATE/architecture_proposal.md,.github/ISSUE_TEMPLATE/audit_report.md, and.github/pull_request_template.md.TRIAGE.md, the architecture and feature issue templates, and the PR template no longer send outside contributors toactivegraph-vision. They say maintainers check proposals against internal design notes and contributors do not need access. Inline triage principles stay.1.11.0 is not published separately. PyPI still has 1.10.0. This line publishes only 1.12.0; a later 1.11.0 upload would put an older version after a newer one.
The trusted-contributor wording (the @dudizimber carve-out in
CONTRIBUTING.md, and the difference versusTRIAGE.md) was left unchanged on purpose. That policy is the maintainer's call.Test plan
git diff --check origin/main...HEADis cleanmkdocs build --strictsucceeded (docs-only; fast tests and mypy not run)