Compare commits

..

11 Commits

Author SHA1 Message Date
azy5030 97e47f3ffe dev-util/gitea-runner: bump to 3.0.0 (#11)
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 2.0.1 to 3.0.0.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v3.0.0
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-3.0.0-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #11
2026-09-20 15:40:42 -05:00
azy5030 0bc4250f39 dev-util/gitea-runner: bump to 2.3.0 (#10)
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 2.0.1 to 2.3.0.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v2.3.0
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-2.3.0-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #10
2026-09-20 15:31:42 -05:00
azy5030 dcf58084cd dev-util/gitea-runner: bump to 2.2.0 (#9)
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 2.0.1 to 2.2.0.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v2.2.0
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-2.2.0-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #9
2026-09-20 15:22:11 -05:00
azy5030 e37bcb66ab dev-util/gitea-runner: bump to 2.1.0 (#8)
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 2.0.1 to 2.1.0.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v2.1.0
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-2.1.0-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #8
2026-09-20 15:09:57 -05:00
gitea-actions 45d3e68c56 dev-util/gitea-runner: bump to 2.0.1
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
2026-07-14 01:21:44 +00:00
gitea-actions 678edf1f37 dev-util/gitea-runner: bump to 2.0.0
CI / lint (push) Has been cancelled
CI / build (push) Has been cancelled
2026-07-01 05:08:29 +00:00
azy5030 7dc4ace3d5 ci(bump): gate toolchain install behind a cheap version check; fix binpkg verify (#4)
CI / lint (push) Successful in 1m58s
CI / build (push) Successful in 6m11s
## Why

The daily **Bump** job (`runs/107` and every other scheduled run) does ~5–26 min
of work on every run before it ever checks whether a bump is needed — and on the
common no-op day it isn't. Timeline of a no-op run:

`docker pull stage3` → `emerge-webrsync` → **`emerge … dev-lang/go dev-util/pkgdev` (29 pkgs)** → `bump-version.sh` finds `already at latest` and exits in **1 second**.

`go`/`pkgdev`/`xz`/`jq` are only needed when a bump actually happens. Recent
no-op scheduled runs took 5m, 26m, 9m, 5m, 10m — all to do nothing.

Separately, the log on every emerge was flooded with binpkg GPG failures
(`unknown key`, `pubring.kbx: No such file`, `Try running getuto`). The
`sed 's/^verify-signature = true/.../'` matched nothing in the stage3 binhost
config, so the intended "disable binpkg signature verification" never took
effect (it worked anyway only because the failures are non-fatal).

## What

- **`bump.yaml`**: add a cheap `Check whether a bump is needed` step that compares
  the newest upstream release (`releases.rss`) against the newest committed ebuild
  (Gitea contents API) using only base-image `wget`, and gate `Sync ::gentoo`,
  the toolchain install, and the bump step on its `needed` output. The gate only
  short-circuits when **confident** (both versions parsed and current ≥ upstream);
  on any doubt — failed fetch, unparseable version — it falls through to the full
  run, where `bump-version.sh` remains the source of truth and re-checks.
- **`bump.yaml` + `ci.yaml`**: replace the no-op `sed` with `sed -i '/^verify-signature/d'`
  + append `verify-signature = false`, so the knob is actually set regardless of
  the stage3 default contents.

## Notes / limits

- The job `container:` still pulls `gentoo/stage3` before the gate runs, so the
  ~3.5 min image pull on no-op days is unchanged; this saves the larger
  webrsync + 29-package emerge. A follow-up could split the gate into a separate
  container-less job to skip the pull too, but that depends on what the runner
  maps `runs-on: ubuntu-latest` to, so it's left out here.
- Validated: `yamllint -c .yamllint.yaml` clean on both files; version-comparison
  logic and the contents-API JSON parsing unit-tested locally (equal / upstream-newer /
  current-ahead / parse-failure cases).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #4
Co-authored-by: Ali Zein Yousuf <azy5030@gmail.com>
Co-committed-by: Ali Zein Yousuf <azy5030@gmail.com>
2026-06-19 21:03:06 -05:00
azy5030 37f78fe356 dev-util/gitea-runner: bump to 1.0.8 (#3)
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 1.0.7 to 1.0.8.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v1.0.8
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-1.0.8-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #3
2026-06-14 01:04:27 -05:00
azy5030 8099407c6c dev-util/gitea-runner: bump to 1.0.7 (#2)
CI / build (push) Has been cancelled
Automated bump of `dev-util/gitea-runner` from 1.0.4 to 1.0.7.

- Upstream release: https://gitea.com/gitea/runner/releases/tag/v1.0.7
- Vendor tarball: https://git.azy.dev/azy5030/azy5030-overlay/releases/tag/gitea-runner-1.0.7-vendor

Review checklist:
- [ ] LICENSE still covers all vendored module licenses (`go-licenses report ./...`)
- [ ] BDEPEND Go version matches upstream go.mod (set to >=1.26.0)
- [ ] version ldflags path `internal/pkg/ver.version` unchanged upstream

CI build + `gitea-runner --version` passed in this workflow.

---------

Co-authored-by: gitea-actions <actions@azy.dev>
Reviewed-on: #2
Co-authored-by: azy5030 <azy5030@gmail.com>
Co-committed-by: azy5030 <azy5030@gmail.com>
2026-06-14 00:41:01 -05:00
azy5030 a05bca6f01 fix(bump): fetch upstream go.mod via /api/v1 raw endpoint
CI / build (push) Successful in 6m8s
Same login-redirect issue as the source archive: gitea.com/gitea/runner/raw/tag/v*/go.mod now 303s to /user/login, so curl -fsSL saves the login HTML, grep finds no 'go N.N' line, and pipefail aborts the bump.

Switching to /api/v1/repos/gitea/runner/raw/go.mod?ref=v* — anonymous, returns the raw go.mod.
2026-06-14 00:28:11 -05:00
gitea-actions 1a87cc50e9 dev-util/gitea-runner: bump to 1.0.6
CI / build (push) Has been cancelled
2026-06-14 00:08:39 -05:00
8 changed files with 246 additions and 10 deletions
+34 -2
View File
@@ -10,21 +10,53 @@ jobs:
container:
image: gentoo/stage3:amd64-openrc
steps:
# Cheap gate: compare the newest upstream release against the newest
# committed ebuild using only base-image tools (wget). The expensive
# toolchain install + bump below is skipped on the common no-op day, so a
# daily run that has nothing to do finishes in seconds instead of minutes.
# bump-version.sh re-checks this itself and remains the source of truth.
- name: Check whether a bump is needed
id: check
env:
BUMP_TOKEN: ${{ secrets.BUMP_TOKEN }}
run: |
latest=$(wget -qO- https://gitea.com/gitea/runner/releases.rss \
| grep -oE '<title>v[0-9]+\.[0-9]+\.[0-9]+</title>' \
| head -1 | sed -E 's#</?title>##g; s/^v//')
current=$(wget -qO- --header="Authorization: token ${BUMP_TOKEN}" \
"${GITHUB_SERVER_URL}/api/v1/repos/${GITHUB_REPOSITORY}/contents/dev-util/gitea-runner" \
| grep -oE '"name": *"gitea-runner-[0-9.]+\.ebuild"' \
| sed -E 's#.*gitea-runner-([0-9.]+)\.ebuild.*#\1#' | sort -V | tail -1)
echo "upstream=${latest} current=${current}"
# Only short-circuit when we are CONFIDENT there is nothing to do
# (both versions parsed and current is >= upstream). On any doubt
# fall through to the full run and let bump-version.sh decide.
if [ -n "$latest" ] && [ -n "$current" ] \
&& [ "$(printf '%s\n%s\n' "$current" "$latest" | sort -V | tail -1)" = "$current" ]; then
echo "needed=false" >> "$GITHUB_OUTPUT"
echo "nothing to do (upstream ${latest}, have ${current})"
else
echo "needed=true" >> "$GITHUB_OUTPUT"
fi
- name: Sync ::gentoo
if: steps.check.outputs.needed == 'true'
run: emerge-webrsync
- name: Configure portage + install tooling
if: steps.check.outputs.needed == 'true'
run: |
mkdir -p /etc/portage/repos.conf
printf '[DEFAULT]\nmain-repo = gentoo\n\n[gentoo]\nlocation = /var/db/repos/gentoo\n' \
> /etc/portage/repos.conf/gentoo.conf
sed -i 's/^verify-signature = true/verify-signature = false/' \
/etc/portage/binrepos.conf/gentoo.conf
sed -i '/^verify-signature/d' /etc/portage/binrepos.conf/gentoo.conf
printf '\nverify-signature = false\n' >> /etc/portage/binrepos.conf/gentoo.conf
emerge -q --getbinpkg \
dev-vcs/git net-misc/curl app-arch/xz-utils app-misc/jq \
dev-lang/go dev-util/pkgdev
- name: Check for new release and open PR
if: steps.check.outputs.needed == 'true'
env:
BUMP_TOKEN: ${{ secrets.BUMP_TOKEN }}
run: |
+44 -4
View File
@@ -2,7 +2,43 @@ name: CI
on: [push]
jobs:
# Lint gate: runs on the plain Docker-backend runner (not the Gentoo
# container) and must pass before the build job starts. Mirrors the lint job
# in the homeserver repo; `just lint` runs markdownlint/shellcheck/yamllint/
# actionlint over the repo.
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# setup-just fetches its binary from GitHub; on a Gitea runner the default
# github-token is the *Gitea* token (GitHub rejects it 401), so pass none
# and use GitHub's unauthenticated API.
- uses: extractions/setup-just@v4
with:
github-token: ""
- uses: taiki-e/install-action@v2
env:
GITHUB_TOKEN: ""
with:
tool: shellcheck
- name: Install markdownlint-cli
run: npm install -g markdownlint-cli
# actionlint has no maintained setup-action and uv ships via astral.sh;
# both installers hit their own release assets (no GitHub token needed).
- name: Install yamllint + actionlint tooling
run: |
curl -LsSf https://astral.sh/uv/install.sh | env UV_INSTALL_DIR=/usr/local/bin sh
bash <(curl -fsSL https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash) latest /usr/local/bin
- name: Run linters
run: just lint
build:
needs: lint
# The label only schedules the job on the (Docker-backend) runner; the steps
# actually run inside the Gentoo container declared below.
runs-on: ubuntu-latest
@@ -22,12 +58,16 @@ jobs:
mkdir -p /etc/portage/repos.conf
printf '[DEFAULT]\nmain-repo = gentoo\n\n[gentoo]\nlocation = /var/db/repos/gentoo\n' \
> /etc/portage/repos.conf/gentoo.conf
sed -i 's/^verify-signature = true/verify-signature = false/' \
/etc/portage/binrepos.conf/gentoo.conf
sed -i '/^verify-signature/d' /etc/portage/binrepos.conf/gentoo.conf
printf '\nverify-signature = false\n' >> /etc/portage/binrepos.conf/gentoo.conf
emerge -q --getbinpkg net-misc/curl dev-util/pkgcheck
# Place this overlay at /var/db/repos/azy5030. actions/checkout is avoided
# (SHA-256 Gitea repos break it); curl + tar fetches the source archive.
# Place this overlay at /var/db/repos/azy5030 via curl + tar. actions/checkout
# can't run here: this job uses the gentoo/stage3 container, and the Gitea
# runner executes JS actions with `node` *inside* that container
# (`docker exec node …`) — stage3 ships no node, so checkout fails with
# exit 127. (The lint job uses actions/checkout fine: it has no container:
# and runs in the runner's default node-capable image.)
- name: Check out overlay
env:
TOKEN: ${{ github.token }}
+9
View File
@@ -0,0 +1,9 @@
{
"MD013": false,
"MD024": {
"siblings_only": true
},
"MD060": {
"style": "compact"
}
}
+85
View File
@@ -0,0 +1,85 @@
# CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## What this is
A personal **Gentoo ebuild repository (overlay)**, repo name `azy5030`, EAPI 8,
`masters = gentoo`, thin + unsigned Manifests (`metadata/layout.conf`). It packages
software not in the main `::gentoo` tree. Currently one package:
`dev-util/gitea-runner`. Hosted on a self-hosted Gitea at `git.azy.dev`. (This repo
is a standard SHA-1 repo; the sibling `homeserver` repo is SHA-256, so workflow
snippets copied from it may carry a `GIT_DEFAULT_HASH: sha256` checkout override
that this repo must *not* use.)
## The vendored-build model (the core design)
`dev-util/gitea-runner` is a `go-module` ebuild built **offline** from upstream
`gitea/runner` source. Gentoo's build sandbox has no network, so Go modules cannot be
fetched at build time. Instead they are vendored ahead of time:
1. The upstream source archive is `SRC_URI`'d from gitea.com's `/api/v1/.../archive`
endpoint (a plain `git clone`/`go get` is never used).
2. A **vendor tarball** (`${P}-vendor.tar.xz`, the result of `go mod vendor`, packed
deterministically) is uploaded as a **release asset on this repo** and is the second
`SRC_URI`. `S="${WORKDIR}/runner"`.
3. `dev-util/gitea-runner/Manifest` pins BLAKE2B/SHA512 of both tarballs. `emerge`
verifies against the Manifest, then compiles offline from `vendor/`.
Consequences when editing the ebuild:
- `LICENSE` must cover **every vendored module's** license, not just upstream's MIT.
The bump PR checklist suggests `go-licenses report ./...` to confirm.
- `BDEPEND` Go version tracks upstream's `go.mod` `go` directive.
- The version string is injected via ldflags into
`gitea.com/gitea/runner/internal/pkg/ver.version`; CI asserts `gitea-runner --version`
echoes `v${PV}`. If upstream moves that symbol path, the build "succeeds" but reports
the wrong version.
## Bumping to a new upstream version
This is **automated** by `scripts/bump-version.sh` (run daily by `bump.yaml`, or
`workflow_dispatch`). To do it manually you must reproduce its steps, because a version
bump is never just renaming the ebuild — the vendor tarball must be regenerated and
re-uploaded as a release asset, or the build will fail Manifest verification. The script:
1. Reads the latest `vX.Y.Z` from upstream `releases.rss`; compares to the newest
committed ebuild. Exits early if up to date or if a `bump/gitea-runner-<ver>` branch
already exists.
2. Downloads the source archive, runs `go mod vendor`, packs a reproducible
`*-vendor.tar.xz` (`--sort=name --mtime='UTC 1970-01-01' --owner=0 --group=0`).
3. Creates/reuses a release tagged `${PN}-${ver}-vendor` and uploads the tarball asset.
4. `git mv`s the ebuild to the new version, rewrites `BDEPEND`'s Go version from
upstream `go.mod`, and regenerates the Manifest with `pkgdev manifest` (after copying
both distfiles into `/var/cache/distfiles` and wiring a temporary `repos.conf`).
5. Validates: `pkgcheck scan`, then `emerge` + `gitea-runner --version | grep v${ver}`.
6. Commits, pushes the branch, opens a PR against `master`.
Requires a `BUMP_TOKEN` repo secret (scopes: repository read/write, write release) plus
a Gentoo env with `go pkgdev git curl xz jq`.
## CI (`.gitea/workflows/ci.yaml`)
Runs on every push, two jobs. A **`lint`** job runs on the plain Docker-backend runner
(no container), checks out with `actions/checkout`, installs the linters, and runs
`just lint` (markdownlint/shellcheck/yamllint/actionlint). The **`build`** job has
`needs: lint` (lint is a gate) and runs inside a `gentoo/stage3:amd64-openrc` container:
`emerge-webrsync` to sync `::gentoo` → configure portage (disables binpkg signature
verification so prebuilt deps like `dev-lang/go` are pulled, not compiled) → **check out
via `curl + tar`, not `actions/checkout`** into `/var/db/repos/azy5030` → `pkgcheck scan`
→ `emerge` → assert `gitea-runner --version` matches the ebuild version.
The build job can't use `actions/checkout` (even though the lint job does): the Gitea
runner executes JS actions by `docker exec node …` *inside* the job container, and
`gentoo/stage3` ships no node, so any JS action fails with exit 127. The lint job has no
`container:`, so it runs in the runner's default node-capable image and checkout works.
## Conventions / gotchas
- **YAML** is linted by `.yamllint.yaml` (relaxed: line-length and document-start
disabled; `truthy.check-keys: false` so `on:` is allowed unquoted).
- `metadata/md5-cache/` is **gitignored** — portage regenerates it on sync, so never
commit it (a stale `gitea-runner-1.0.4` file may linger on disk untracked).
- The bump script and CI deliberately preserve the scheme of `GITHUB_SERVER_URL`: on the
self-hosted runner it is an internal `http://` endpoint. Don't hardcode `https`.
- New packages must be added to `profiles/categories` (currently just `dev-util`).
+70
View File
@@ -0,0 +1,70 @@
# azy5030 overlay management commands
# Install dev tooling (linters) used by the lint recipes and CI
setup-dev:
brew install just markdownlint-cli shellcheck actionlint uv
# Lint Markdown: all repo files, or only the .md files in a passed list
lint-md files="":
#!/usr/bin/env bash
set -euo pipefail
if [ -z "{{files}}" ]; then
markdownlint --ignore node_modules '**/*.md'
else
targets=$(printf '%s\n' {{files}} | grep -E '\.md$' || true)
if [ -n "$targets" ]; then markdownlint --ignore node_modules $targets; fi
fi
# Lint shell scripts: all repo files, or only the .sh files in a passed list
lint-sh files="":
#!/usr/bin/env bash
set -euo pipefail
if [ -z "{{files}}" ]; then
targets=$(find . -name '*.sh' -not -path './node_modules/*')
else
targets=$(printf '%s\n' {{files}} | grep -E '\.sh$' || true)
fi
if [ -n "$targets" ]; then shellcheck $targets; fi
# Lint YAML: all repo files, or only the .yaml/.yml in a passed list (via uv)
lint-yaml files="":
#!/usr/bin/env bash
set -euo pipefail
if [ -z "{{files}}" ]; then
targets=$(find . \( -name '*.yaml' -o -name '*.yml' \) -not -path './node_modules/*')
else
targets=$(printf '%s\n' {{files}} | grep -E '\.ya?ml$' || true)
fi
if [ -n "$targets" ]; then uvx yamllint $targets; fi
# Lint Gitea Actions workflows: all, or only the workflow files in a passed list
lint-actions files="":
#!/usr/bin/env bash
set -euo pipefail
if [ -z "{{files}}" ]; then
targets=$(find .gitea/workflows \( -name '*.yaml' -o -name '*.yml' \) 2>/dev/null || true)
else
targets=$(printf '%s\n' {{files}} | grep -E '^\.gitea/workflows/.*\.ya?ml$' || true)
fi
# actionlint also runs shellcheck on each `run:` block. No custom runner
# labels here (workflows use ubuntu-latest), so no -config-file is needed.
if [ -n "$targets" ]; then actionlint $targets; fi
# Autofix all Markdown files
fix-md:
markdownlint --fix --ignore node_modules '**/*.md'
# Apply shellcheck's auto-fixable suggestions to all shell scripts
fix-sh:
#!/usr/bin/env bash
set -euo pipefail
targets=$(find . -name '*.sh' -not -path './node_modules/*')
# shellcheck's diff carries ./ path segments that `git apply` rejects; strip them.
diff=$(shellcheck -f diff $targets 2>/dev/null | sed 's|/\./|/|g' || true)
if [ -n "$diff" ]; then printf '%s\n' "$diff" | git apply; fi
# Lint everything (all repo files, or only a passed list of files)
lint files="": (lint-md files) (lint-sh files) (lint-yaml files) (lint-actions files)
# Autofix everything
fix: fix-md fix-sh
+2 -2
View File
@@ -1,2 +1,2 @@
DIST gitea-runner-1.0.7-vendor.tar.xz 3018704 BLAKE2B 39b861b1b454a22f23c80bacd551127d0812b71a336c79032fa01f8df834eca23e030479da76fc12358af955f7cb56bcc541b99df1fd7880a62fbf35b8859d4c SHA512 0f21ba48db4bbb9fc0738543a7123e884e93ab5b423b6ff99dfa913d6df6cf0db4d96bff2e32b82beee9fef8e81cfdef849d58050fe8d9a2abddb55af7da8a38
DIST gitea-runner-1.0.7.tar.gz 340157 BLAKE2B 7dc0fb3026e02c14052d4983f265adf787d9f3f01d856e81a4297a3163a1d2efe19f5ae6b9132fe4520ca551c84e7749ea33c7eeff87806870b0a9b60c54719f SHA512 8f0c69bb0e416efca1b63ae37cad0f740a5093bc569711b9327cd11a69f40d1037e59dc547ad3a88e8d6be7fa669a3acf58ac775237932f2872c492a7812cf96
DIST gitea-runner-3.0.0-vendor.tar.xz 3221008 BLAKE2B 98de6b01e06d5c6f797e9f9c4cad72a492c4fd50263d63fbb233384d5a6fdea8a44d3aee23145884c23ad4667445eb3b3960b382d6cac59c10f99f1ffa30abb8 SHA512 a63e24ca573bead0cc9a83dd09f04ec732004b6a0cfe6c9d578c09c41b50f3c74a9a6468d01526f1373b7bda037719c43157ba7e6d4608cb84dd8a6ecc6b4b39
DIST gitea-runner-3.0.0.tar.gz 469896 BLAKE2B 32328f3a704bc26a5d5931cb221dce130ee03ef2117f91d31e84354f2a377e344a77e586e73b9e5cb5715d305ea4dc0bc49f6a4bb442aead51d29ebdab88f79a SHA512 7759ddde6a71cab0ac40499ef1d75825dca3aac0a5c76696e21b0d05f88e1b6b7cb6e2fb9e14efd64e462259520cf6dc0441d0dc9f7db98dd9fc70783629e0f3
+2 -2
View File
@@ -11,7 +11,7 @@ set -euo pipefail
PN="gitea-runner"
UPSTREAM_RSS="https://gitea.com/gitea/runner/releases.rss"
UPSTREAM_ARCHIVE="https://gitea.com/api/v1/repos/gitea/runner/archive"
UPSTREAM_GOMOD="https://gitea.com/gitea/runner/raw/tag"
UPSTREAM_GOMOD="https://gitea.com/api/v1/repos/gitea/runner/raw/go.mod"
: "${BUMP_TOKEN:?BUMP_TOKEN is required}"
: "${GITHUB_SERVER_URL:?GITHUB_SERVER_URL is required}"
@@ -82,7 +82,7 @@ git checkout -b "$branch"
git mv "${pkgdir}/${PN}-${current}.ebuild" "${pkgdir}/${PN}-${latest}.ebuild"
# Track the upstream go.mod's required Go version in BDEPEND.
goreq=$(curl -fsSL "${UPSTREAM_GOMOD}/v${latest}/go.mod" \
goreq=$(curl -fsSL "${UPSTREAM_GOMOD}?ref=v${latest}" \
| grep -oE '^go [0-9]+\.[0-9]+(\.[0-9]+)?' | awk '{print $2}')
[ -n "$goreq" ] && sed -i -E \
"s#^BDEPEND=\">=dev-lang/go-[0-9.]+\"#BDEPEND=\">=dev-lang/go-${goreq}\"#" \