ci: publish each Eco mod with scoped LFS assets

coilyco-ops commented

2026-07-22 08:09:33 +00:00

Member

Build the C# mod collection in the pinned AOS CI container, route NuGet through the Forgejo runner egress proxy, and publish one deterministic Forgejo generic package per Mods/UserCode mod. Each package job must fetch only its own Git LFS objects, fail if any LFS pointer remains in the archive input, preserve the install-ready Mods/UserCode/ layout, use the existing organization package token, and support workflow dispatch. CI must not materialize or rebuild the full Unity project.

Build the C# mod collection in the pinned AOS CI container, route NuGet through the Forgejo runner egress proxy, and publish one deterministic Forgejo generic package per Mods/UserCode mod. Each package job must fetch only its own Git LFS objects, fail if any LFS pointer remains in the archive input, preserve the install-ready Mods/UserCode/<Mod> layout, use the existing organization package token, and support workflow dispatch. CI must not materialize or rebuild the full Unity project.

coilyco-ops referenced this issue

2026-07-22 08:18:23 +00:00

fix: make consolidated repo pre-commit configs root-aware #7

coilyco-ops referenced this issue from a commit

2026-07-22 08:19:58 +00:00

ci: publish each Eco mod with scoped LFS assets

coilyco-ops commented

2026-07-22 08:20:54 +00:00

Author

Member

Push run 5 failed only in the mods job after seven seconds. Root hygiene and secret scanning passed, and all nine package jobs correctly skipped behind the failed dependency. The workflow exported the runner proxy only inside the final dotnet step, while the earlier validate-ci Ward verb invokes uv to materialize the locked Python environment. The next correction moves HTTP_PROXY and HTTPS_PROXY into GITHUB_ENV before all dependency-bearing Ward commands, keeping checkout and internal Forgejo traffic direct.

coilyco-ops referenced this issue from a commit

2026-07-22 08:21:33 +00:00

fix(ci): proxy all dependency setup

coilyco-ops commented

2026-07-22 08:25:59 +00:00

Author

Member

Exact AOS v0.255.0 reproduction found the startup failure. The image passed python-syntax, validate-ci, and test-mod-packages, then lint-mod-packages failed because the repo invoked a global ruff executable that the image does not provide. The repo now declares ruff in its development dependency group, locks ruff 0.15.22, and invokes it through uv. The same four CI startup verbs all pass inside the exact pinned image before this correction is pushed.

coilyco-ops referenced this issue from a commit

2026-07-22 08:26:12 +00:00

fix(ci): lock the package lint tool

coilyco-ops commented

2026-07-22 08:28:24 +00:00

Author

Member

Completed and verified. Push run 7 succeeded in 29 seconds on commit a12bb5d. Root hygiene, offline secret scanning, the locked package-tool tests and lint, and the proxy-backed .NET build all passed. Nine independent package jobs succeeded, including the mods with scoped Git LFS runtime bundles. Guarded workflow-dispatch run 8 then succeeded in 28 seconds against the same commit, proving the manual path and byte-identical idempotent re-publication. The full Unity source tree was never materialized or rebuilt.

Completed and verified. Push run 7 succeeded in 29 seconds on commit a12bb5d. Root hygiene, offline secret scanning, the locked package-tool tests and lint, and the proxy-backed .NET build all passed. Nine independent package jobs succeeded, including the mods with scoped Git LFS runtime bundles. Guarded workflow-dispatch run 8 then succeeded in 28 seconds against the same commit, proving the manual path and byte-identical idempotent re-publication. The full Unity source tree was never materialized or rebuilt.

coilyco-ops closed this issue

2026-07-22 08:28:25 +00:00

Rows
Columns

ci: publish each Eco mod with scoped LFS assets #6