Commit graph

4 commits

Author SHA1 Message Date
MiTHRAL
a813e12277 Use upload-artifact@v3 for Gitea compatibility
All checks were successful
Build & Release Pack / build (push) Successful in 3m11s
upload-artifact@v4 requires the GitHub-only artifact v2 API
(GHESNotSupportedError on Gitea). v3 uses the v1 protocol that
Gitea's act_runner implements, and is mirrored on the Forgejo
mirror.
2026-08-19 15:41:57 -04:00
MiTHRAL
c9c33c48c5 Make CI validation stdlib-only for Python 3.9 runner container
Some checks failed
Build & Release Pack / build (push) Failing after 1m56s
The node:20-bullseye runner image ships Python 3.9, which lacks
tomllib (3.11+). Extract inline workflow validation into
tools/validate_pack.py using regex-based parsing of the machine-
generated packwiz TOML subset, and call it from the workflow.
2026-08-19 15:38:29 -04:00
MiTHRAL
48b31d7d44 Replace softprops release action with native Gitea API release
Some checks failed
Build & Release Pack / build (push) Failing after 59s
softprops/action-gh-release@v1 is not mirrored on the Forgejo action
mirror, which fatally aborted the job at action-download. Create the
release via the Gitea REST API using the built-in GITHUB_TOKEN and
upload both pack artifacts directly.
2026-08-19 15:33:43 -04:00
MiTHRAL
167249fcc8 Add Gitea Actions CI/CD workflow for pack build and release
Builds the client pack on the media-server docker runner: refreshes the
packwiz index, runs integrity + download-resolvability checks, exports
Modrinth (.mrpack) and CurseForge (.zip) artifacts, validates the
CurseForge manifest completeness, uploads artifacts, and publishes a
release on v* tags.
2026-08-19 15:29:15 -04:00