CI
May 24, 2026 ยท View on GitHub
GitHub Actions
Workflows
| Workflow | Trigger | Role |
|---|---|---|
audit | Schedule | Audit security |
ci | Push, PR | Test, Lint, Coverage |
release | TagPush | Distribution, GitHub Release |
release_image | TagPush | PushDockerImage |
website | Push, PR | Update website |
audit
It is scheduled to run periodically, updating the advisory database for cargo audit to the latest version before executing cargo audit
ci
Continuous integration is executed, and test coverage is uploaded to Codecov.
When Dependabot updates dependencies and it is a patch version, it automatically merges the changes.
release
The workflow generated by dist(cargo-dist) creates binaries and a GitHub release when a tag is pushed.
Whether a package is included in this workflow is controlled by the [package.metadata.dist.dist] section in the Cargo.toml file.
release_image
Build the package's docker image and push it to the registry
website
The workflow generated by oranda generate ci uploads the project's website to GitHub Pages.
Secrets
| Secret | Usage | GeneratedAt | ManagedBy |
|---|---|---|---|
CACHIX_AUTH_TOKEN | Read and Write cachix cache | cachix | @ymgyt |
CODECOV_TOKEN | Upload test coverage to codecov | codecov | @ymgyt |
HOMEBREW_TAP_TOKEN | Push to homebrew repo by cargo-dist | github | @ymgyt |
NPM_TOKEN | Push to npm registry by cargo-dist | npm | @ymgyt |
HOMEBREW_TAP_TOKEN
- cargo-dist doc
reposcope is required
NPM_TOKEN
- cargo-dist doc
- Packages and scopes: Read and write
- Select packages: All packages (NOTE: because the package does not yet exist, you must pick this. However, you can (and probably should!) update this to scope the token to a single package after publish. This is sadly a limitation of the npm token system.)
- Organizations: No access