docs: move release notes into CHANGELOG.md#32
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Moves the fork’s release history out of README.md into a dedicated CHANGELOG.md, and updates the README to link to it.
Changes:
- Removed embedded changelog content from
README.mdand replaced it with a link toCHANGELOG.md. - Added
CHANGELOG.mdcontaining release notes for v0.14.5 through v0.14.15 plus0.14.6-PRE.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| README.md | Replaces inline changelog section with a link to the standalone changelog. |
| CHANGELOG.md | Adds consolidated fork release history entries and download notes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Apple Silicon (M1/M2/M3):** \`Chorus-aarch64.app.zip\` or \`Chorus-aarch64.dmg\` | ||
| - **Intel:** \`Chorus-x86_64.app.zip\` or \`Chorus-x86_64.dmg\` |
There was a problem hiding this comment.
The download filenames here are wrapped in escaped backticks (`...`), which will render as literal backticks instead of inline code. Remove the backslash escaping so the filenames are formatted consistently with the other release entries.
|
|
||
| Released 2026-04-08 | ||
|
|
||
| This is a testing build which should have the same feature-set as v0.14.14. Intended use is for proof-of-concept for merging with base fork meltylabs/chorus |
There was a problem hiding this comment.
This paragraph reads like a run-on sentence and ends without punctuation. Consider splitting into two sentences and clarifying what “base fork meltylabs/chorus” refers to (e.g., “upstream meltylabs/chorus”), then add a trailing period.
| > xattr -d com.apple.quarantine /Applications/Chorus.app | ||
| > ``` | ||
|
|
||
| ## 0.14.6-PRE (pre-release) |
There was a problem hiding this comment.
Version headings in this file mostly use a leading "v" (e.g., "v0.14.14"). If the pre-release tag also uses that convention, consider renaming this heading to match for easier scanning and consistent linking.
Summary
Test Plan