Repository navigation
docs: date the 1.4.0 changelog, add known limits and publish the changelog as release notes - #59
Merged
Merged
Conversation
…gelog as release notes The 1.4.0 heading said 2026-10-23 although the section was edited until the tag day; it now carries the release date. Known limits (code questions with small models, slow research on CPU, what was not measured) are listed in both changelogs and READMEs. The release workflow used --generate-notes, which lists PR titles and would drop those limits. It now publishes the version's CHANGELOG section (scripts/release_notes.py) and fails when the section is missing or empty. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: TrinaxCode <185935802+TrinaxCode@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
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
Prepares the 1.4.0 release notes:
[1.4.0]in both changelogs is dated 2026-10-26 (it said 2026-10-23, but the section was edited until the tag day). If the tag is pushed on another day, change this date first.docs/CHANGELOG.md,docs/CHANGELOG.es.md,README.mdandREADME.es.md: code questions with small local models, slowtrinaxai researchon CPU, and what has not been measured (Windows end to end, GPU, large models).--generate-notes, which lists PR titles and would drop those limits. It now publishes the version's CHANGELOG section throughscripts/release_notes.py, and the job fails if that section is missing or empty (before anything is staged or published).Type of change
Checklist
ruff check,ruff format --check,mypy,pytest(full suite, plus the newtests/test_release_notes.py),npm test,npm audit,pip-auditandscripts/public_readiness.pypass.python scripts/public_readiness.py).GITHUB_REF_NAMEonly through the shell environment, as the existing steps do.Related Issues
None.
🤖 Generated with Claude Code