Skip to content

docs: document release:assets convention in README #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kirgene merged 1 commit into from
Jun 5, 2026
Merged

docs: document release:assets convention in README #77

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,9 @@ This feature is particularly useful for:
- If a `package.json` is present in the root of the repository and it does not have
private=true, the package will be published to npm for
the applicable branches and tags.
- If a `release:assets` script is present in `package.json`, it is run during
the build with the output directory as its argument, and the files it
produces there are uploaded as assets to the GitHub release/prerelease.
- The following scripts are expected in the `package.json` file:
- `lint`
- `dep:check`
Expand Down