Skip to content

ci: default published install checks to latest #13

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
mertushka merged 1 commit into from
Jun 13, 2026
Merged

ci: default published install checks to latest #13

Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions .github/workflows/published-install.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ on:
workflow_dispatch:
inputs:
package_spec:
description: npm package spec to install
description: npm package spec to install (tag or exact version)
required: true
default: "@mertushka/webrtc-node@next"
default: "@mertushka/webrtc-node@latest"
workflow_run:
workflows: ["Release"]
types: [completed]
Expand Down
4 changes: 3 additions & 1 deletion docs/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,9 @@ The `Published Install` workflow runs after a successful `Release` workflow or
by manual dispatch. It installs the published npm package on Linux glibc, Linux
musl, macOS x64, macOS arm64, Windows x64, and Windows arm64, then verifies both
CommonJS and ESM imports. It sets `WEBRTC_NODE_PREBUILD_ONLY=1` so missing or
broken release assets fail instead of compiling from source.
broken release assets fail instead of compiling from source. Manual runs default
to the `latest` npm tag; pass an explicit package version or prerelease tag when
validating another publication.

The install script downloads the target archive and its sibling `.sha256`
release asset. It enforces download limits, verifies the SHA-256 digest, accepts
Expand Down
Loading