[Feature] Use GitHub-native generated release notes#753
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b372a930d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 22f28ebb07
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e80ee4fd80
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Task
Contract
How to Verify
Main Scenario
Action: merged PR publish reaches the release path.
Expected result: the workflow no longer runs the legacy
changelog generateaction, andyarn release createasks GitHub to generate release notes through the GitHub Releases API before creating each release.Additional Scenario
Action: run
yarn test unit release-create --test-reporter=tap.Expected result: release note generation uses package-specific previous tags and a target commitish for new release tags.
Proofs
yarn test unit release-create --test-reporter=tapyarn typecheckandyarn lintfor changed release filesyarn workspace @atls/code-github buildyarn workspace @atls/yarn-plugin-release buildyarn workspace @atls/yarn-cli buildcmp -s yarn/cli/dist/yarn.mjs .yarn/releases/yarn.mjsyarn raijin:checkyarn check