Zakaria El OrcheandClaude Sonnet 5
3f0b49fa36
Publish Maven packages / publish (push) Successful in 1m55s
Root cause of the persistent 401s found: Gitea's own per-job GITEA_TOKEN cannot publish to any package registry at all — a known, still- unimplemented limitation (go-gitea/gitea#23642), not a settings.xml auth-format issue as first assumed. Confirmed by testing: GITEA_TOKEN authenticated fine against the plain API but every registry write endpoint rejected it regardless of scope or header style. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
50 lines
2.6 KiB
YAML
50 lines
2.6 KiB
YAML
name: Publish Maven packages
|
|
|
|
# Flash's own POM keeps `2.1.0-SNAPSHOT` as its committed version — that's what local
|
|
# `mvn install` (Pathway's normal dev loop, see its pom.xml `flash.version` comment) always
|
|
# produces, and changing it here would break that. Gitea's Maven registry, unlike a real
|
|
# snapshot repository, refuses to re-publish an existing name+version (must delete first —
|
|
# see https://docs.gitea.com/usage/packages/maven#publish-a-package), so every push instead
|
|
# publishes under a throwaway version stamped with the commit it built from
|
|
# (`2.1.0-<short-sha>`), via `versions:set` on a checkout copy — never touching the committed
|
|
# POMs. Consumers (Pathway's `docker` Maven profile) pin `flash.version` to one specific
|
|
# published build and bump it by hand to pick up newer Flash changes; see
|
|
# pathway/pom.xml's `docker` profile for the other half of this.
|
|
on:
|
|
push:
|
|
branches: [master]
|
|
|
|
jobs:
|
|
publish:
|
|
runs-on: ubuntu-latest
|
|
# No actions/checkout here on purpose: it's a Node-based action, and this container
|
|
# (chosen for its preinstalled mvn/JDK 21) has no Node — checkout would fail with
|
|
# "node: executable file not found". A plain git clone needs neither.
|
|
container:
|
|
image: maven:3.9-eclipse-temurin-21
|
|
steps:
|
|
- name: Checkout
|
|
run: |
|
|
apt-get update && apt-get install -y --no-install-recommends git
|
|
git clone https://git.pixel-services.com/Relism/Flash5.git .
|
|
git checkout ${{ gitea.sha }}
|
|
|
|
- name: Stamp every module with a commit-scoped version
|
|
run: |
|
|
SHORT_SHA=$(git rev-parse --short HEAD)
|
|
mvn -B versions:set -DnewVersion="2.1.0-${SHORT_SHA}" -DprocessAllModules=true -DgenerateBackupPoms=false
|
|
echo "Publishing as 2.1.0-${SHORT_SHA}"
|
|
|
|
- name: Deploy to the Gitea Maven registry
|
|
env:
|
|
# Not GITEA_TOKEN: Gitea's own job token can't publish to package registries at
|
|
# all (a known, still-unimplemented limitation — see
|
|
# https://github.com/go-gitea/gitea/issues/23642). Confirmed by testing: GITEA_TOKEN
|
|
# authenticated fine against the plain API but still got 401 from this endpoint no
|
|
# matter the auth style. PACKAGES_TOKEN is a real PAT with write:package scope.
|
|
PACKAGES_TOKEN: ${{ secrets.PACKAGES_TOKEN }}
|
|
run: |
|
|
mvn -B -s .gitea/maven-settings.xml -DskipTests deploy \
|
|
-DaltReleaseDeploymentRepository=gitea::https://git.pixel-services.com/api/packages/Relism/maven \
|
|
-DaltSnapshotDeploymentRepository=gitea::https://git.pixel-services.com/api/packages/Relism/maven
|