Repository navigation
docs: prepare 1.11 changelog and release content review - #15236
Merged
Merged
Conversation
Make the release notes easier to review by grouping accessibility changes and trimming implementation details while retaining compatibility effects and contributor credits. Include eight omitted landed changes and the bundled Deno macOS requirement. Preserve the existing regression-fix membership, which signals stable backports.
Make pre-release changelog verification and website/blog preparation repeatable without mixing content work with release publication. Require merged stable-backport evidence for regression-section moves and preserve entry identities, contributor credits, and compatibility effects during editorial reorganization.
Use repository identity and upstream source refs for content research so the skill works without a personal checkout layout. Require a local checkout only for destination edits or rendering, and derive review output locations from the task or repository conventions.
Use quarto-dev/quarto-web at prerelease for unreleased highlights and documentation, recording the reviewed commit without assuming a local checkout layout.
Route release claims to relevant CLI rules and website preparation to the upstream workflow, authoring, image and blog sources. Keep screenshots, scan baselines, runtime checks and release merges conditional so ordinary content reviews load only the guidance they need.
Make the blog skill and release-announcement reference accessible without a local quarto-web checkout, while retaining commit-specific evidence guidance.
Make website rules, conditional skill references and blog authoring sources directly accessible online. Keep branch links current while requiring commit-specific evidence for each release review.
Independent highlights and blog drafts exposed ambiguous audit scope, a missed documentation include, and misleading subtree-squash output. Scope full changelog accounting to changelog edits, follow partials before declaring documentation gaps, and inspect imports with a restricted first-parent diff. Keep release verification in quarto-cli and destination execution in the existing website and publishing workflows.
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Preserve the reviewed 1.11 changelog and the new Windows offline-script entry from main so release preparation includes both changes.
Reachable documentation can still contradict a highlighted capability. Require agreement on version, output format and syntax before selecting a supporting link, with shared corrections routed through the destination workflow.
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.
Description
Preparing the 1.11 release exposed missing changelog entries and the need for a repeatable way to verify release content before writing website highlights and the announcement post.
The changelog is completed and clarified. Accessibility and command changes are grouped by what the reader is trying to do. Contributor credits and the existing Regression fixes membership are preserved, and dependency versions follow the committed lockfile.
A new project skill,
review-release-content, covers checking release claims, stable backports and supporting documentation. It links to the website and blog authoring workflows, and finds repositories through upstream refs rather than personal checkout paths. Supporting links used in highlights are read for agreement with the claim (syntax, version, output format) instead of only checking that the anchor exists. That check applies only to claims that involve syntax.Validation: Markdown parsing, skill validation and
git diff --checkpass. Two independent runs exercised highlights and preliminary blog drafting. Rendering the destination pages and running the blog examples are still pending.Checklist
I have (if applicable):
AI-assisted PR
Note: autonomous AI agents submitting PRs without human oversight are not permitted — see the Code of Conduct.