Phylax Systems Actions

A repository of useful actions we use across the repositories at Phylax Systems.

Original inspiration (and probably quite a few of workflows) originate from init4/actions. They are re-used under their Apache 2.0 License.

npm trusted publishing

The release-npm action publishes through npm's OpenID Connect integration without an NPM_TOKEN. Run it as a step in the repository's release workflow so npm can match the trusted publisher directly to that workflow file. The job must grant id-token: write and contents: read.

jobs:
  release-npm:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: phylaxsystems/actions/release-npm@main

Configure the caller's workflow filename as the trusted publisher on npm. The legacy reusable release-npm.yaml workflow remains available for existing callers, but the step action avoids reusable-workflow identity mismatches during npm's OIDC token exchange.

For a non-destructive retry of an existing tag, dispatch the caller workflow and pass that tag through the action's release_tag input. The action checks out the tag and verifies it still matches package.json before publishing.

Rust base feature matrices

Control which feature combinations run for test, clippy, and docs using matrix inputs testfeature-sets. Each takes a JSON string array where each element (e.g., "" for default, "--all-features", "--no-default-features --features=foo") triggers a separate job run with those flags passed to cargo. The default is [""].

• Default only: feature-sets: '[""]'
• Test default & "foo" feature: feature-sets: '["", "--features=foo"]'
• Test "bar" without defaults: feature-sets: '["--no-default-features --features=bar"]'

Rust test CLI arguments

You can pass additional CLI arguments to the cargo test command using the test-args input parameter. This allows you to customize test execution with flags like --release, --bin, --lib, or any other cargo test options.

• Run tests in release mode: test-args: '--release'
• Run only binary tests: test-args: '--bin my-binary'
• Run with multiple flags: test-args: '--release --verbose'

Cargo nextest support

You can optionally use cargo nextest instead of the default cargo test by setting the use-nextest parameter to true. Nextest provides faster test execution and better output formatting.

• Use nextest: use-nextest: true
• Use default cargo test: use-nextest: false (default)

When use-nextest is enabled, the workflow will automatically install cargo-nextest and run cargo nextest run instead of cargo test. All other parameters like test-args and feature-sets work the same way with both test runners.

Zepter feature propagation

Set enable-zepter: true to add a zepter job that lints feature propagation across the workspace (e.g. when crate A depends on B and both expose a std feature, A's std must enable B's std). Zepter is a static manifest linter — it does not compile.

The calling repo must provide a zepter config (.zepter.yaml, zepter.yaml, or .config/zepter.yaml) declaring which features to check and which lints to enforce. The job runs zepter run check and fails if propagation is inconsistent.

• Enable: enable-zepter: true
• Disabled by default so existing callers are unaffected.