Skip to content

chore(main): release zapi 3.1.1#51

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--zapi
Open

chore(main): release zapi 3.1.1#51
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--zapi

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.1.1 (2026-07-20)

Bug Fixes

  • dsl: support class pointer arguments (#50) (9dd2111)

Code Refactoring

  • js: unify env lifecycle refcounting (#53) (d3d5056)

Miscellaneous Chores

  • define changelog sections for release-please (#54) (1c5e7b4)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch from 1fda9bd to 7feca1e Compare July 14, 2026 12:22
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch from 7feca1e to e63c595 Compare July 20, 2026 04:03
wemeetagain pushed a commit that referenced this pull request Jul 20, 2026
## Summary

Add an explicit `changelog-sections` config to
`release-please-config.json` so generated release notes group commits
into named sections.

Visible sections: Features, Bug Fixes, Performance Improvements, Code
Refactoring, Dependencies, Reverts, Miscellaneous Chores, Documentation.

Hidden types (`build`, `ci`, `test`, `style`) are marked `hidden: true`
so they don't clutter the changelog.

## Motivation

With the default release-please changelog config, only `feat` and `fix`
map to visible sections; other conventional-commit types (including
`refactor`) are hidden. As a result, #53 (`refactor(js): unify env
lifecycle refcounting`) was merged but did **not** appear in the open
release PR #51, whose changelog only shows the `Bug Fixes` entry for
#50.

Adding `refactor` → "Code Refactoring" (and the other types above) as
visible sections ensures such changes are reflected in future release
notes.

## Test plan

- [x] JSON validated (`python3 -m json.tool`)
- Config takes effect on the next release-please run

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch from e63c595 to 79bfe7d Compare July 20, 2026 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants