CI: refine build numbering, release/publish flow

Compute BUILD_NUMBER relative to the last gradle.properties mcVersion change (instead of total commits), add dependabot groups for actions and gradle deps, and simplify release notes formatting (disable generated notes and inline metadata). Remove the Publish-To-Repo step from the main build workflow and add a force-push input/conditional to publish-api workflow. Invoke scripts/SetENV.sh in publish-api and update SetENV.sh to produce jar names that omit run attempt suffix for first run. These changes tighten publishing controls and make build numbering reflect per-version increments.
This commit is contained in:
2026-07-09 20:18:43 +08:00
parent a6b1cf1e28
commit 5ce33501cd
4 changed files with 52 additions and 33 deletions
+5 -1
View File
@@ -15,7 +15,11 @@ release=$(prop release)
pushRepo=$(prop pushRepo)
release_tag="$mcversion-$commitid"
run_attempt="${GITHUB_RUN_ATTEMPT:-1}"
jarName="$project_id-$mcversion-$BUILD_NUMBER-$run_attempt.jar"
if [ "$run_attempt" = "1" ]; then
jarName="$project_id-$mcversion-$BUILD_NUMBER.jar"
else
jarName="$project_id-$mcversion-$BUILD_NUMBER-$run_attempt.jar"
fi
jarName_dir="camellia-server/build/libs/$jarName"
flag_push_repo=false