Repository navigation
Simplify the release skills to start, changelog and check - #1820
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
katarinasupe
changed the title
write-changelog-item still pointed to Release Notes Required and Memgraph PRs Docs Needed. It now uses the Docs Integration Tracking sections that new-release-branch creates and check-release-milestone reads.
The MAIN/REPLICA rule now lives in write-docs-page's tone.md, so engineers writing docs follow it too. Step 6 points there instead of keeping its own copy.
write-changelog-item now links the docs page (and section) for a change in its entry, and check-release-milestone checks that every Docs needed entry has that link.
…anch The skill now reads the version from the Memgraph milestone, creates the docs milestone that write-docs-page targets, puts the release PR in it, and appends the DOCS link to the Memgraph milestone description instead of replacing it.
Drop the grammar and cross-link steps: write-docs-page and CI cover them per PR. Report in chat instead of a Cursor canvas, drop the local tracking file, and name the skill after its folder.
Lead a bug-fix entry with what works now, not how it used to fail. Also name the skill after its folder.
katarinasupe
force-pushed
the
update/changelog-skill-sections
branch
from
October 13, 2026 09:12
a17cada to
b1c3f6d
Compare
katarinasupe
changed the title
check-release now works out what is missing from the milestones and labels, so the release PR no longer keeps a tracking checklist.
check-release works out what is missing from the Memgraph milestone, the docs labels and the docs milestone instead of a checklist in the release PR, and on release day sets the dates, updates the download links and closes the docs milestone.
katarinasupe
changed the title
The release PR keeps the Docs Integration Tracking checklist between markers. check-release rebuilds it from the labels and milestones on every run and ticks items from what is merged and in the release notes, so nobody edits it by hand.
write-changelog-item reads the corrections the writing skill lists for a series of product PRs, and check-release points to them from the overview. check-release also skips the release PR when matching docs PRs to product PRs.
The overview starts with a Progress section: merged out of open and merged PRs, overall and for PRs that need docs or a release note, so it's clear how much docs work can be done now and how much has to wait.
check-release collects the Noticed, not fixed items from the release's docs PRs, lists them in the overview, and fixes them in one PR into the release branch. The docs PR template has both sections the release check reads, each with a note to keep its heading and format.
Keep this branch's write-changelog-item, drop pre-release (its sitemap rule is not needed) and skills/README.md (AGENTS.md lists the skills).
…on the examples check in check-release
…ior that ships, and tidy write-changelog-item
This branch was successfully deployed
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.
Simplifies the release skills to three, one per step of a release:
release/<version>and the docs milestone thatwrite-docs-pagetargets, opens the release PR in that milestone and links it from the Memgraph milestone. Handles patch releases (3.13.2).Release note correctionsfor the product PR's series, whichcheck-releasepoints to from the overview.check-release-milestoneandpre-release) finds what the release still needs from the Memgraph milestone, docs labels, docs PRs and the docs milestone, and runspnpm check. On release day it sets the dates, updates the download links and, after the merge, creates the GitHub release and closes the docs milestone.It also collects the problems docs PRs noticed outside their own change (
Noticed, not fixed) and fixes them in one PR per release, into the release branch. The docs PR template now has both sections the release check reads, each with a note to keep its heading and format.The release PR keeps the Docs Integration Tracking overview, but
check-releaserebuilds it from the labels and milestones on every run and ticks items from what is merged, so nobody edits it by hand. The grammar and cross-link steps are gone:write-docs-pageand CI cover them per PR. Skill names match their folders, andAGENTS.mdlists the three.pnpm checknow also fails when a##section of the release notes appears twice, which happened when a patch release was merged into an open release branch.