Johan LEROY
bd76e53570
All checks were successful
CI / Build & test (Node 22) (push) Successful in 10m15s
CI / Build & test (Node 24) (push) Successful in 10m10s
CI / No em/en dashes (push) Successful in 3s
Desktop Release / Build Linux (AppImage + deb) (push) Successful in 14m1s
CI / Pack & boot smoke (Node 22) (push) Successful in 10m5s
L'attache des installeurs/VSIX à la release Gitea réutilise NPM_TOKEN ; ce token doit porter write:repository EN PLUS de write:package, sinon l'API release renvoie 403 (l'étape est best-effort, non bloquante : les artefacts restent disponibles via upload-artifact).
76 lines
3.5 KiB
YAML
76 lines
3.5 KiB
YAML
# Packaging du VSIX de l'extension VS Code, déclenché UNIQUEMENT par un tag vscode-vX.Y.Z
|
|
# (séparé de la release du daemon, qui écoute les tags v*). Le .vsix est exposé en artefact du run
|
|
# (toujours) et, en best-effort, attaché à la release Gitea correspondante.
|
|
name: VSCode Release
|
|
|
|
on:
|
|
push:
|
|
tags: ['vscode-v*']
|
|
|
|
permissions:
|
|
contents: write
|
|
|
|
jobs:
|
|
package:
|
|
name: Package VSIX
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
- uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 22
|
|
cache: npm
|
|
- run: npm ci
|
|
# Garde-fou : le tag (sans "vscode-v") doit correspondre à la version du manifeste de l'extension.
|
|
- name: Verify tag matches extension version
|
|
run: |
|
|
pkg=$(node -p "require('./packages/vscode/package.json').version")
|
|
tag="${GITHUB_REF_NAME#vscode-v}"
|
|
if [ "$pkg" != "$tag" ]; then
|
|
echo "ERREUR: tag '$tag' != version extension '$pkg'"
|
|
exit 1
|
|
fi
|
|
echo "OK: tag $tag == version $pkg"
|
|
# Build du shared puis bundle esbuild de l'extension (typecheck inclus), puis packaging VSIX.
|
|
# --no-dependencies : tout est bundlé dans dist/extension.js → pas de node_modules dans le VSIX.
|
|
- name: Build & package
|
|
run: |
|
|
npm run build:vscode
|
|
version=$(node -p "require('./packages/vscode/package.json').version")
|
|
cd packages/vscode
|
|
npx --yes @vscode/vsce package --no-dependencies -o "git-arboretum-${version}.vsix"
|
|
# Artefact du run : canal de distribution fiable, indépendant de l'API release.
|
|
# upload-artifact@v3 : Gitea Actions ne supporte pas @v4 (@actions/artifact v2+).
|
|
- uses: actions/upload-artifact@v3
|
|
with:
|
|
name: vsix
|
|
path: packages/vscode/*.vsix
|
|
# Best-effort : attache le VSIX à la release Gitea du tag (crée la release si absente).
|
|
# Réutilise le secret NPM_TOKEN (même token Gitea que la publication du daemon) : ce token doit
|
|
# porter write:repository en plus de write:package, sinon l'API release renvoie un 403. Sans
|
|
# token, l'étape est ignorée sans faire échouer le job (continue-on-error) ; le VSIX reste
|
|
# disponible en artefact.
|
|
- name: Attach VSIX to Gitea release
|
|
continue-on-error: true
|
|
env:
|
|
RELEASE_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
run: |
|
|
if [ -z "$RELEASE_TOKEN" ]; then
|
|
echo "::notice::NPM_TOKEN absent : VSIX disponible en artefact uniquement."
|
|
exit 0
|
|
fi
|
|
api="${GITHUB_SERVER_URL}/api/v1/repos/${GITHUB_REPOSITORY}"
|
|
auth="Authorization: token ${RELEASE_TOKEN}"
|
|
version=$(node -p "require('./packages/vscode/package.json').version")
|
|
vsix="packages/vscode/git-arboretum-${version}.vsix"
|
|
# id de release du tag, sinon création
|
|
rid=$(curl -fsSL -H "$auth" "${api}/releases/tags/${GITHUB_REF_NAME}" | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).id || ''" || true)
|
|
if [ -z "$rid" ]; then
|
|
rid=$(curl -fsSL -X POST -H "$auth" -H 'Content-Type: application/json' \
|
|
-d "{\"tag_name\":\"${GITHUB_REF_NAME}\",\"name\":\"Arboretum VSCode ${version}\"}" \
|
|
"${api}/releases" | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).id || ''")
|
|
fi
|
|
curl -fsSL -X POST -H "$auth" -F "attachment=@${vsix}" \
|
|
"${api}/releases/${rid}/assets?name=git-arboretum-${version}.vsix"
|
|
echo "VSIX attaché à la release ${GITHUB_REF_NAME}."
|