AegisGitea-MCP

4 Commits

Include renames

Author	SHA1	Message	Date
Latte	e5dfba208e	ci: publish package on merge to dev/main with separate dev and stable packages Replace the tag-only publish trigger (no v* tags ever existed, so the package was never built) with branch-push publishing: - dev push -> aegis-gitea-mcp-dev at X.Y.Z.dev<run_number> (always unique) - main push -> aegis-gitea-mcp at X.Y.Z, a clean no-op via uv --check-url if that version is already in the registry Name + version are patched into pyproject.toml at build time only; the committed file keeps aegis-gitea-mcp / X.Y.Z. Lint + test gates still run before publish, and the REGISTRY_TOKEN secret is required (fail-closed).	2026-06-27 15:59:30 +02:00
Latte	4db37d200e	ci: stop artifact upload from failing the build on Gitea runners docker / test (push) Successful in 34s Details docker / lint (push) Successful in 40s Details lint / lint (push) Successful in 43s Details docker / lint (pull_request) Successful in 43s Details docker / test (pull_request) Successful in 34s Details test / test (push) Successful in 44s Details lint / lint (pull_request) Successful in 44s Details test / package (push) Successful in 1m8s Details test / test (pull_request) Successful in 44s Details test / package (pull_request) Successful in 53s Details docker / docker (push) Successful in 1m5s Details docker / docker (pull_request) Successful in 43s Details Gitea's act_runner does not reliably support the actions/upload-artifact@v4 backend. Drop the artifact upload from the test workflow (the package job's purpose is to build and smoke-test, not to store wheels) and make the publish workflow's upload best-effort (continue-on-error) so a flaky artifact backend cannot block a release — the package is still published to the registry.	2026-06-27 15:26:56 +02:00
LatteandClaude Opus 4.8	1ca5bcbc6b	ci: reuse existing REGISTRY_TOKEN secret for package publish docker / test (pull_request) Successful in 34s Details test / test (pull_request) Successful in 43s Details docker / docker (pull_request) Successful in 39s Details docker / test (push) Successful in 34s Details docker / lint (push) Successful in 40s Details test / test (push) Successful in 42s Details lint / lint (push) Successful in 44s Details docker / lint (pull_request) Successful in 44s Details lint / lint (pull_request) Successful in 42s Details docker / docker (push) Successful in 46s Details The repo already has a write:package REGISTRY_TOKEN secret (used by docker.yml). Reuse it for uv publish instead of requiring new GITEA_PACKAGE_* secrets: authenticate as GITHUB_ACTOR with the token as password. Update packaging docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-27 14:46:44 +02:00
LatteandClaude Opus 4.8	499bf98d92	ci: build and publish package to Gitea registry on tag docker / test (push) Successful in 38s Details lint / lint (push) Successful in 45s Details docker / lint (push) Successful in 44s Details test / test (push) Successful in 44s Details docker / docker (push) Successful in 40s Details docker / lint (pull_request) Successful in 40s Details docker / test (pull_request) Successful in 34s Details lint / lint (pull_request) Successful in 41s Details test / test (pull_request) Successful in 40s Details docker / docker (pull_request) Successful in 37s Details Add .gitea/workflows/publish.yml: on a v* tag, gate on the existing lint + test jobs, then build sdist+wheel with uv and publish to the self-hosted Gitea PyPI registry using least-privilege Actions secrets (GITEA_PACKAGE_USER / GITEA_PACKAGE_TOKEN). The job fails loudly when the secrets are absent rather than publishing anonymously, uploads the built artifacts, and leaves a disabled public-PyPI stub. Public PyPI is intentionally not published in this pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-27 11:18:07 +02:00