chore(main): release 0.1.7#41
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 552d1b12a3
ℹ️ 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".
|
|
||
| ### Features | ||
|
|
||
| * add release automation and product docs ([64b2e5a](https://github.com/hack-dance/stack/commit/64b2e5a5c9182c649452c4bbb0e372808a976cc2)) |
There was a problem hiding this comment.
Regenerate 0.1.7 notes from commits after v0.1.6
The new 0.1.7 section is pulling in commits that were already released earlier (for example 64b2e5a is already listed under 0.1.4 and is an ancestor of the 0.1.6 parent), even though this release header says it covers v0.1.6...v0.1.7. This makes the changelog/release notes materially inaccurate by presenting old work as newly shipped in 0.1.7, which can mislead users and any tooling that consumes CHANGELOG entries.
Useful? React with 👍 / 👎.
552d1b1 to
6d17d5f
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6d17d5fa11
ℹ️ 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".
| ## [0.1.7](https://github.com/hack-dance/stack/compare/v0.1.6...v0.1.7) (2026-03-26) | ||
|
|
||
|
|
||
| ### Bug Fixes |
There was a problem hiding this comment.
Include merged feature commits in 0.1.7 changelog
The new 0.1.7 section only lists bug fixes, but this release also brings in new feat: commits (for example 920c7b4 and 1867aeb, merged via b1d236a) that are not documented anywhere in CHANGELOG.md. Omitting those shipped features makes the release notes materially incomplete for users and tooling that rely on changelog entries to understand behavior changes.
Useful? React with 👍 / 👎.
🤖 I have created a release beep boop
0.1.7 (2026-03-26)
Bug Fixes
This PR was generated with Release Please. See documentation.