* fix(publish): add aardvark-sys version and publish it before main crate - Add version = "0.1.0" to aardvark-sys path dependency in Cargo.toml - Update all three publish workflows to publish aardvark-sys first - Add aardvark-sys COPY to Dockerfile for workspace builds - Fixes cargo publish failure: "dependency aardvark-sys does not specify a version" * ci: publish aardvark-sys before main crate in all publish workflows All three crates.io publish workflows now publish aardvark-sys first, wait for indexing, then publish the main zeroclawlabs crate. |
||
|---|---|---|
| .. | ||
| checks-on-pr.yml | ||
| ci-run.yml | ||
| cross-platform-build-manual.yml | ||
| master-branch-flow.md | ||
| pub-aur.yml | ||
| pub-homebrew-core.yml | ||
| pub-scoop.yml | ||
| publish-crates-auto.yml | ||
| publish-crates.yml | ||
| README.md | ||
| release-beta-on-push.yml | ||
| release-stable-manual.yml | ||
| tweet-release.yml | ||
Workflow Directory Layout
GitHub Actions only loads workflow entry files from:
.github/workflows/*.yml.github/workflows/*.yaml
Subdirectories are not valid locations for workflow entry files.
Repository convention:
- Keep runnable workflow entry files at
.github/workflows/root. - Keep cross-tooling/local CI scripts under
dev/orscripts/ci/when used outside Actions.
Workflow behavior documentation in this directory:
.github/workflows/master-branch-flow.md