Files
grpc-library/.gitea/workflows/release.yml
T
DongHyeonka 8d705bcaaf
main / main-check (push) Successful in 5m22s
fix(ci): JDK를 Temurin 목록에 있는 이름으로 고정한다
main.yml 첫 실행(Gitea run 1)이 setup-java에서 멈췄다: 「Could not find
satisfied version for SemVer '21.0.11+10'」. Temurin이 내놓는 이름은
`21.0.11+10.0.LTS`다. 템플릿 setup-gradle-java action에서 그대로 가져온
값이라 템플릿에서도 같은 이유로 깨질 수 있다(템플릿 Actions는 아직 꺼져
있어 드러나지 않았다).

같은 21.0.11 빌드를 목록의 이름 그대로 적는다. `21`처럼 줄만 적으면 새
패치가 나올 때마다 빌드 JDK가 말없이 바뀐다.

검증: Gitea run 1 로그의 사용 가능 목록에 21.0.11+10.0.LTS가 있다. 고친
workflow의 실행 결과는 이 커밋의 main 실행이다.
2026-11-08 11:22:12 +09:00

43 lines
1.9 KiB
YAML

# Release stage, on a vMAJOR.MINOR.PATCH tag (docs/work/release.md). One Gradle invocation:
# `releaseCheck` (certification and integration lanes, version, SBOM, dependency gate) and then
# `release` (publish every module and the SBOM to Gitea Packages, signed, and read the version back
# anonymously). Publishing starts only after releaseCheck has passed, so a red check leaves nothing
# half-published (Gitea refuses a second upload of a version).
#
# Secrets (repository settings, created by the owner): PACKAGES_TOKEN, a personal access token with
# package read/write only (the job token cannot publish packages); SIGNING_KEY, an ASCII-armoured PGP
# secret key; SIGNING_PASSWORD, its passphrase.
name: release
on:
push:
tags: ["v*"]
permissions:
contents: read
jobs:
release:
runs-on: ubuntu-latest
timeout-minutes: 90
steps:
- uses: https://github.com/actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
- uses: https://github.com/actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00 # v4.7.1
with:
distribution: temurin
java-version: "21.0.11+10.0.LTS"
- uses: https://github.com/gradle/actions/setup-gradle@3f131e8634966bd73d06cc69884922b02e6faf92 # v6
with:
build-scan-publish: false
cache-read-only: true
# The tag names the version: ca.java-conventions refuses any RELEASE_TAG that is not
# vMAJOR.MINOR.PATCH. releaseCheck is named although release depends on it, because
# verifyStrictLaneStages counts a stage only when a command names it.
- run: ./gradlew releaseCheck release --stacktrace
env:
RELEASE_TAG: ${{ github.ref_name }}
PACKAGES_TOKEN: ${{ secrets.PACKAGES_TOKEN }}
SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
SIGNING_PASSWORD: ${{ secrets.SIGNING_PASSWORD }}
TESTCONTAINERS_REUSE_ENABLE: "false"