Skip to content

chore(main): release zapi 4.0.0 - #51

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

chore(main): release zapi 4.0.0#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

4.0.0 (2026-07-29)

⚠ BREAKING CHANGES

  • manage external buffer lifetime (#66)
  • require writable external buffer storage (#58)

Bug Fixes

  • dsl: support class pointer arguments (#50) (9dd2111)
  • harden N-API boundary against JS-triggerable memory bugs (#60) (fff76f3)
  • manage external buffer lifetime (#66) (d134a6a)
  • napi: receive raw pointer out parameters (#57) (fde4a9a)
  • remove redundant platform check from musl detection (#64) (0d4829c)
  • require writable external buffer storage (#58) (8fd898f)
  • restore registerDecls on Zig 0.16 (#59) (7f3af3e)

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 3 times, most recently from 6090c9d to 7257a99 Compare July 24, 2026 15:35
@github-actions github-actions Bot changed the title chore(main): release zapi 3.1.1 chore(main): release zapi 4.0.0 Jul 27, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch 3 times, most recently from dcc7de3 to b4838c9 Compare July 27, 2026 11:30
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch from b4838c9 to 172a960 Compare July 28, 2026 06:45
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--zapi branch from 172a960 to f43c9bd Compare July 29, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant