Skip to content
 
 

Repository files navigation

Threshold CI

Maintained GitHub Actions and a reusable Solidity documentation workflow for Threshold repositories. This fork includes the vendored npm-version-bump action; see UPSTREAM.md for provenance and retained licenses.

Action Purpose
actions/load-env-variables Load public environment configuration from the pinned revision
actions/upstream-builds-query Extract versions and URLs from completed build payloads
actions/notify-workflow-completed Notify the Threshold release manager of a completed build
actions/run-workflow Dispatch the next configured Threshold workflow
actions/npm-version-bump Compute and write a package prerelease version

Consumers pin actions and .github/workflows/reusable-solidity-docs.yml to a reviewed full commit SHA. Each action directory documents its inputs. MIGRATION.md describes coordinated consumer changes, credentials, and rollout order. Do not use the inherited v2 tags for the maintained actions.

Solidity documentation previews

The reusable Solidity docs workflow can post an artifact preview link when both exportAsGHArtifacts and commentPR are enabled for a pull request. Commenting defaults to false; callers that enable it must grant pull-requests: write to the workflow's GITHUB_TOKEN. Sequential runs update the comment identified by projectDir, so separate projects in the same PR keep separate comments; overlapping runs of the same projectDir are not serialized and may leave duplicate preview comments. Only comments authored by github-actions[bot] with the project's preview marker are updated. Older unmarked comments and comments written by other users are left untouched.

Development

Use Node 24 and run:

npm ci
npm run lint
npm test
npm run build
npm run check:bundles

Commit regenerated dist files with source changes. Tests include local/mock registry and dispatch checks; they do not publish packages or invoke release workflows. check:bundles runs the shipped bundles outside the source tree with no node_modules directory. This repository is not published to npm.

The release manager is manually dispatched via main.yml. Its source and configuration come from the default branch; upstream_ref selects consumer branches. It requires CI_GITHUB_TOKEN with Actions write permission on this repository and the three configured consumer repositories. Public configuration in config/env contains no credentials; use GitHub secrets for credentials.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages