rename: cloud-installer → cloud-sync
CI / build (push) Failing after 3s
CI / release (push) Has been skipped

'installer' implied one-way install (matching packwiz-installer); this
tool is bidirectional sync (pull on launch, push on exit). Aligns with
the existing automc <scope>-<role> pattern: cloud-svc ↔ cloud-sync,
matching mc-router, mc-wrapper, gate-waker.

Gitea repo renamed via API (id 2974 preserved); jar filename now
cloud-sync-<version>.jar. Build verified post-rename.
This commit is contained in:
2026-06-02 20:25:27 +02:00
parent 6ab43a168e
commit ed4115cba8
6 changed files with 21 additions and 21 deletions
+4 -4
View File
@@ -26,8 +26,8 @@ jobs:
if: startsWith(github.ref, 'refs/tags/v')
uses: actions/upload-artifact@v4
with:
name: cloud-installer-jar
path: build/libs/cloud-installer-*.jar
name: cloud-sync-jar
path: build/libs/cloud-sync-*.jar
release:
runs-on: ubuntu-latest
@@ -38,7 +38,7 @@ jobs:
- uses: actions/download-artifact@v4
with:
name: cloud-installer-jar
name: cloud-sync-jar
path: build/libs/
- name: Publish release
@@ -51,7 +51,7 @@ jobs:
-d "{\"tag_name\":\"${tag}\",\"name\":\"${tag}\",\"draft\":false,\"prerelease\":false}" \
"${GITEA_SERVER_URL}/api/v1/repos/${{ gitea.event.repository.full_name }}/releases" > /tmp/release.json
release_id=$(jq -r .id /tmp/release.json)
for jar in build/libs/cloud-installer-*.jar; do
for jar in build/libs/cloud-sync-*.jar; do
curl -sS -X POST \
-H "Authorization: token ${gh_token}" \
-F "attachment=@${jar}" \