The initial import copied the runner LICENSE verbatim, including portions
credited to the Gitea Authors and to GitHub. Neither body of material is here:
the Gitea Actions protocol definitions stay in the runner under crates/runner-control-gitea/proto/ with their own LICENSE and UPSTREAM,
and the hashFiles bundle stays next to the worker that runs it. No file in crates/ carries a derivation notice, so LICENSE is now plain MIT.
README
Rewritten. It said consumers embed this repository as a submodule and depend on
the crates by path, which is wrong — they depend on a git URL pinned to a
commit. The section arguing why Gitea and Forgejo appear in the source is
gone; they are context names in a syntax the compiler reads, which needs no
defence.
Manifests
Crate manifests now inherit version, edition and lints from the workspace root.
That was previously forbidden because path dependencies made these crates
members of the consumer workspace; with a git dependency they resolve their own
root, so the rule lost its reason and check-architecture.sh no longer asserts
it.
.editorconfig loses its [Makefile] section, copied from the runner, which
has a Makefile while this repository does not.
## LICENSE
The initial import copied the runner `LICENSE` verbatim, including portions
credited to the Gitea Authors and to GitHub. Neither body of material is here:
the Gitea Actions protocol definitions stay in the runner under
`crates/runner-control-gitea/proto/` with their own `LICENSE` and `UPSTREAM`,
and the `hashFiles` bundle stays next to the worker that runs it. No file in
`crates/` carries a derivation notice, so `LICENSE` is now plain MIT.
## README
Rewritten. It said consumers embed this repository as a submodule and depend on
the crates by path, which is wrong — they depend on a git URL pinned to a
commit. The section arguing why `Gitea` and `Forgejo` appear in the source is
gone; they are context names in a syntax the compiler reads, which needs no
defence.
## Manifests
Crate manifests now inherit version, edition and lints from the workspace root.
That was previously forbidden because path dependencies made these crates
members of the consumer workspace; with a git dependency they resolve their own
root, so the rule lost its reason and `check-architecture.sh` no longer asserts
it.
`.editorconfig` loses its `[Makefile]` section, copied from the runner, which
has a `Makefile` while this repository does not.
## Verification
`cargo fmt --check`, `cargo clippy --workspace --all-targets --all-features -- -D warnings`,
`cargo test --workspace --all-targets --all-features` (23 tests),
`check-architecture.sh`, `check-rust-loc.sh`.
The initial import copied the runner LICENSE, which credits the Gitea and
GitHub authors for the vendored Actions protocol and the hashFiles bundle.
Neither lives here, so document where they do and state the provenance rule.
Co-authored-by: Cursor <cursoragent@cursor.com>
The README explained why other vendors are named in the source and how to
embed the repository as a submodule. The first is noise, the second is
wrong: consumers depend on a git URL pinned to a commit.
Co-authored-by: Cursor <cursoragent@cursor.com>
day01
changed title from fix: drop third-party copyright notices this repository does not carry to fix: correct the licence and the consumption instructions2026-08-04 22:14:21 +00:00
The repository ships no image, so a Dockerfile only to compile it was a
layer with nothing to produce. The job image already carries cc, git and
curl, so the toolchain action is all that is missing.
Co-authored-by: Cursor <cursoragent@cursor.com>
The runner cannot resolve a ref that looks like a version number, and a
commit is the reference an immutable action should carry anyway.
Co-authored-by: Cursor <cursoragent@cursor.com>
day01
merged commit cef22b4620 into %!s()2026-08-05 04:40:14 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
day01
LICENSE
The initial import copied the runner
LICENSEverbatim, including portionscredited to the Gitea Authors and to GitHub. Neither body of material is here:
the Gitea Actions protocol definitions stay in the runner under
crates/runner-control-gitea/proto/with their ownLICENSEandUPSTREAM,and the
hashFilesbundle stays next to the worker that runs it. No file incrates/carries a derivation notice, soLICENSEis now plain MIT.README
Rewritten. It said consumers embed this repository as a submodule and depend on
the crates by path, which is wrong — they depend on a git URL pinned to a
commit. The section arguing why
GiteaandForgejoappear in the source isgone; they are context names in a syntax the compiler reads, which needs no
defence.
Manifests
Crate manifests now inherit version, edition and lints from the workspace root.
That was previously forbidden because path dependencies made these crates
members of the consumer workspace; with a git dependency they resolve their own
root, so the rule lost its reason and
check-architecture.shno longer assertsit.
.editorconfigloses its[Makefile]section, copied from the runner, whichhas a
Makefilewhile this repository does not.Verification
cargo fmt --check,cargo clippy --workspace --all-targets --all-features -- -D warnings,cargo test --workspace --all-targets --all-features(23 tests),check-architecture.sh,check-rust-loc.sh.@@ -22,6 +22,24 @@ stop matching the plan the control plane believes it produced.The GitHub Actions frontend — workflow reading and model, expressions, contexts,and the action model — moves here alongside it.## Why other vendors appear in the sourceout
fix: drop third-party copyright notices this repository does not carryto fix: correct the licence and the consumption instructions