release:notes: put the release-ledger line under the Packages table
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- release
Research direction
Start with assembleNotes() in scripts/release-notes.mjs, where the Packages, Repository and Release ledger sections are ordered, and read the layout comment at the top of that file. Move the ledger line to directly after the Packages table, then update the expectations in scripts/release-notes.test.mjs. Also update step 5a of the release skill so its ordered list matches. Done means the tests pass and the generated notes show the ledger line right under Packages.
Written by the indexing model from the issue text.
Description
Problem
npm run release:notes (scripts/release-notes.mjs) puts the release-ledger line near the end of the notes, after every package's PR list, the Repository section and GitHub's New Contributors / Full Changelog trailer:
## Packages
## <package> <version> … (one per published package)
## Repository
## New Contributors / Full Changelog
Release ledger: [<branch>](<url>)
## Known issues
## Thanks for helping us improve
In v1.0.0 that was below 102 PR lines, so the evidence for the release was the hardest thing to find. The maintainer moved it by hand, to directly under the Packages table, before publishing (v1.0.0).
Expected
The generator emits the ledger line immediately after the ## Packages table, so a reader sees what was published and the verification behind it together:
## Packages
Release ledger: [<branch>](<url>)
## <package> <version> …
…
Changes together: assembleNotes(), the layout comment at the top of scripts/release-notes.mjs, its tests (scripts/release-notes.test.mjs), and the ordered list in the release skill's step 5a ("Draft the release notes").
- Dominant language
- JavaScript
- Stars
- 91.2k
- Forks
- 11.8k
- Avg merge
- 6h 52m
- Merged PRs (30d)
- 107
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/servers
-
documentation v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/servers#5133 ·
Maintainers usually reply within 1 day
-
sequentialthinking: the thought box's header row is 2 columns narrower than its borderPossibly taken @nightcityblade claimed this 1 day ago. Openbug server-sequentialthinking v2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5108 · 2 comments ·
Maintainers usually reply within 1 day
-
bug server-git v2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5107 ·
Maintainers usually reply within 1 day
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
modelcontextprotocol/servers#5091 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/servers#5071 · 2 comments ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/servers
Similar issues
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jaegertracing/jaeger-ui#4596 ·
Maintainers usually reply within 1 day
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days