Skip to content

Commit e7d924b

Browse files
ovitrifclaude
andcommitted
docs: add release publishing rules to AGENTS.md
- Releases must be published (not draft) and set as latest - Release notes are for binding consumers only — no internal CI/docs/workflow changes Co-Authored-By: Claude Opus 4.6 <[email protected]>
1 parent 888f23e commit e7d924b

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

AGENTS.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,11 +237,15 @@ When bumping the version, ALWAYS update ALL of these files:
237237
shasum -a 256 bindings/swift/LDKNodeFFI.xcframework.zip
238238
# Compare output with the checksum value in Package.swift - they MUST match
239239
```
240-
- Create GitHub release with same name as the tag, upload `LDKNodeFFI.xcframework.zip`
240+
- Create GitHub release as **published** (not draft) and **set as latest release**, with
241+
same name as the tag, upload `LDKNodeFFI.xcframework.zip`
241242
- **Release notes = DELTA only.** Describe only what changed since the previous release
242243
(e.g., rc.31 notes list only changes since rc.30). Do NOT paste the full cumulative
243244
CHANGELOG section — that covers all rc versions combined. Write concise notes covering
244245
the PR's changes: bug fixes, features, optimizations, and binding/version updates.
246+
- Release notes are for **consumers of the bindings** — cover only Rust code changes,
247+
FFI changes, and binding updates. Do NOT include internal CI, documentation, or
248+
workflow changes.
245249
- **ALWAYS add release link at the end of PR description** (use `gh pr edit` to update the body):
246250
```
247251
### Release

0 commit comments

Comments
 (0)