Skip to content

Commit 256a727

Browse files
committed
docs: add binary release workflow notes to CONTRIBUTING
1 parent 62df847 commit 256a727

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

CONTRIBUTING.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,18 @@ lerna publish
7777
This will:
7878
1. Bump versions for changed packages
7979
2. Publish to npm
80-
3. Create git tags (e.g., `markdown-magic@4.0.5`)
80+
3. Create git tags and GitHub releases (e.g., `markdown-magic@4.0.5`)
8181
4. Automatically trigger binary builds via GitHub Actions
8282

83+
### Binary release workflows
84+
85+
Two workflows build platform binaries when releases are created:
86+
87+
- `release-binary-md-magic.yml` - triggers on `markdown-magic@*` releases
88+
- `release-binary-block-parser.yml` - triggers on `comment-block-parser@*` releases
89+
90+
These use the `release: created` event (not `push: tags`) because lerna's `GITHUB_TOKEN` can't trigger workflows on tag push (GitHub prevents this to avoid infinite loops).
91+
8392
### Manual binary release
8493

8594
You can also trigger a binary release manually:

0 commit comments

Comments
 (0)