Commit Graph
140 Commits
Author SHA1 Message Date
renovate[bot]andkolaente 2a9d543442 chore(deps): update pnpm/action-setup action to v6.0.10 2026-08-03 23:47:26 +02:00
kolaente d0a0efd403 ci: auto-regenerate yaegi symbols alongside swagger docs 2026-08-02 16:16:06 +02:00
renovate[bot]andkolaente 06b1c37f18 chore(deps): update docker/login-action action to v4.6.0 2026-07-29 16:41:16 +02:00
renovate[bot]andkolaente d62ce215fa chore(deps): update docker/login-action action to v4.5.2 2026-07-29 09:22:50 +02:00
kolaente b506dfe792 ci: drop unused contents: write from generate-swagger-docs
The job pushes with the SSH deploy key configured by actions/checkout's
ssh-key input, so GITHUB_TOKEN is never used for writes. Scope it down to
contents: read.
2026-07-28 10:42:15 +02:00
renovate[bot]andTink e88ba5a58f chore(deps): update docker/login-action action to v4.5.1 2026-07-24 17:10:02 +00:00
renovate[bot]andkolaente 4688991e0d chore(deps): update docker/login-action action to v4.5.0 2026-07-24 06:44:41 +00:00
renovate[bot]andkolaente 34c1cf30cf chore(deps): update actions/checkout action to v7.0.1 2026-07-21 05:59:31 +00:00
renovate[bot]andTink 838c405667 chore(deps): update actions/setup-node action to v7 2026-07-17 22:35:33 +00:00
renovate[bot]andkolaente 37cf59edf5 chore(deps): update actions/setup-go action to v7 2026-07-17 22:30:01 +00:00
renovate[bot]andkolaente 95b7e673fb chore(deps): update actions/setup-node action to v6.5.0 2026-07-17 10:53:35 +00:00
renovate[bot]andkolaente 05ad8049ef chore(deps): update softprops/action-gh-release action to v3.0.2 2026-07-15 09:15:49 +00:00
renovate[bot]andTink 7c65960c85 chore(deps): update docker/login-action action to v4.4.0 2026-07-03 14:27:17 +00:00
renovate[bot]andkolaente 7f74f1e174 chore(deps): update pnpm/action-setup action to v6 2026-07-02 15:34:30 +00:00
renovate[bot]andkolaente 43adb94e3f chore(deps): update softprops/action-gh-release action to v3 2026-07-02 15:34:18 +00:00
renovate[bot]andTink 2eaa019e64 chore(deps): update docker/metadata-action action to v6.2.0 2026-07-02 13:54:29 +00:00
renovate[bot]andTink 6199189955 chore(deps): update docker/login-action action to v4.3.0 2026-07-02 10:32:16 +00:00
renovate[bot]andkolaente bf7c545716 chore(deps): update docker/build-push-action action to v7 2026-07-02 06:28:29 +00:00
renovate[bot]andkolaente 8c7c74bb86 chore(deps): update docker/login-action action to v4 2026-07-02 06:28:12 +00:00
renovate[bot]andkolaente a968f22449 chore(deps): update docker/metadata-action action to v6 2026-07-02 06:27:45 +00:00
renovate[bot]andkolaente af7775bf00 chore(deps): update github artifact actions 2026-07-01 12:41:34 +00:00
renovate[bot]andkolaente d374c8e6f9 chore(deps): update actions/checkout action to v7 2026-06-28 09:06:15 +00:00
renovate[bot]andkolaente ba5c09f962 chore(deps): update actions/cache action to v6 2026-06-27 19:39:18 +00:00
renovate[bot]andkolaente 07d39b4290 chore(deps): pin dependencies 2026-06-27 18:01:23 +00:00
kolaenteandkolaente be7eabb9b3 ci: move build-mage prep job out of test.yml into release.yml
build_mage_bin is only consumed by publish-repos in release.yml, so it
doesn't belong in the test workflow. Move it to release.yml as a
prep job and add it to publish-repos's needs list.
2026-05-27 13:01:44 +00:00
kolaenteandkolaente ed9df9064c refactor(ci): derive composite-action inputs from project name
Reviewer asked us to stop over-configuring the release-binaries and
release-os-package composite actions — they're called only with
vikunja or veans, so per-project paths, artifact names, cache keys, S3
target, and version-or-unstable can all be derived inside the action
from the project name. The xgo-out-name input goes away too.

Vikunja-specific pre-build (downloading frontend_dist, generating
config.yml.sample) now happens inside the action, gated on the project
input. Callers no longer need those preamble steps.

Secrets stay as inputs — composite actions can't read \`\${{ secrets.* }}\`
directly; passing them through is the simplest workaround.

Each callsite shrinks to ~13 lines of mostly-secret pass-through plus
2-4 lines of real parameters.
2026-05-27 13:01:44 +00:00
kolaenteandkolaente e903b72b9e refactor(ci): call release composite actions from release.yml
Replace the inline bodies of binaries, veans-binaries, os-package, and
veans-os-package jobs with calls to the new release-binaries and
release-os-package composite actions. Each call site is now ~25 lines
of inputs instead of ~75 lines of duplicated mage+upx+gpg+s3 plumbing.

publish-repos switches from the parent's ./mage-static to the
prebuilt build_mage_bin artifact so it can drive build/'s repo metadata
targets inside the publish-repos containers.
2026-05-27 13:01:44 +00:00
kolaenteandkolaente 5f00fca166 feat(veans): build and publish veans alongside vikunja
Cross-compile veans for the same OS/arch matrix as the main vikunja
binary, wrap each into a signed zip, build deb/rpm/apk/archlinux
packages via nfpm, and merge those into the existing dl.vikunja.io
package repos so `apt install veans` works from the same source.

- veans/magefile.go: Release namespace (xgo cross-compile, upx, sha256,
  per-target zip bundle, nfpm.yaml templating).
- veans/nfpm.yaml: minimal — binary at /usr/local/bin/veans, no service
  or postinstall.
- .github/workflows/release.yml: veans-binaries + veans-os-package
  jobs, veans artifacts merged into publish-repos and create-release.
S3 layout mirrors vikunja under /veans/<version>/.
2026-05-27 13:01:44 +00:00
kolaente 0b45cff583 feat(ci): sign archlinux packages with GPG for pacman verification
Pacman verifies individual package signatures (.sig files). Add GPG
setup and detach-sign step for archlinux packages in the os-package
job. The .sig is uploaded alongside the package to S3.
2026-04-14 19:35:23 +02:00
kolaente c970f87e89 fix(ci): resolve symlinks before upload instead of deleting them
S3 can't store symlinks. Previously all symlinks were deleted, which
removed vikunja.db -> vikunja.db.tar.gz needed by pacman. Now resolve
symlinks into real file copies first, then delete package files.
2026-04-14 17:08:27 +02:00
kolaente fdeacd3eaf fix(ci): write GPG key directly to file instead of importing and exporting
No need to import the key into GPG and then export it again. Just
write the secret key data directly to a file for nfpm to use.
2026-04-14 16:22:52 +02:00
kolaente f6ec5d8e96 feat(ci): sign RPM packages with GPG via nfpm
Add GPG signing configuration to nfpm.yaml for rpm packages. The
os-package job now sets up GPG and exports the key for nfpm to use
during package creation.
2026-04-14 15:47:31 +02:00
kolaente 4d8c37f8ff fix(ci): exclude package files from repo metadata upload
The dl.vikunja.io worker redirects package file requests under /repos/
to the existing artifacts, so uploading them again is redundant.
Remove .deb, .rpm, .apk, .archlinux, .pacman, .pkg.tar.zst files
and symlinks before uploading to R2.
2026-04-14 14:36:00 +02:00
kolaente 77167eb356 fix(ci): pin s3-action to main branch 2026-04-14 12:47:18 +02:00
kolaente 3d08a4f78f fix(ci): update s3-action to skip directories during upload
The s3-action glob matched directories causing EISDIR errors. Fixed
the action to filter with fs.statSync().isFile(). Updated all
s3-action references to the new version.
2026-04-14 12:25:43 +02:00
kolaente 797c813091 fix(ci): revert S3 glob to **/* and clean up directories before upload
The **/*.* glob skipped extensionless files like Release, InRelease,
and Packages. Revert to **/* and instead remove reprepro's internal
db/conf directories and directory symlinks before uploading.
2026-04-14 10:02:50 +02:00
kolaente cff690fb5f fix(ci): skip desktop .apk in APK repo, not a valid Alpine package
The desktop .apk file from electron-builder is not an Alpine APK
package and causes apk index to fail with "v2 package format error".
2026-04-13 16:15:41 +02:00
kolaente a110642093 fix(ci): inline APK repo generation to avoid glibc binary on Alpine
The mage-static binary is compiled with glibc which can't run on
Alpine's musl. Instead of fighting compatibility, inline the APK
repo generation as shell commands since the logic is simple.
2026-04-13 15:18:08 +02:00
kolaente 29098aee62 fix(ci): add libc6-compat for Alpine, fix S3 upload glob, add debug
- Install libc6-compat on Alpine so the glibc-linked mage binary runs
- Change S3 upload glob from **/* to **/*.* to skip directories
- Add debug step to inspect mage-static binary on Alpine
2026-04-13 12:13:05 +02:00
kolaente f3aaf27242 fix(ci): set RELEASE_VERSION to avoid git dependency in containers
The mage initVars calls git describe when RELEASE_VERSION is not
set. Setting it avoids needing git in the container images.
2026-04-13 11:45:37 +02:00
kolaente cd61db4415 refactor(ci): split publish-repos into matrix with native containers
Each package format now runs in its native container image:
- apt: ubuntu:noble (reprepro)
- rpm: fedora:latest (createrepo_c)
- pacman: archlinux:latest (repo-add + bsdtar built-in)
- apk: alpine:latest (apk + abuild-sign built-in)

This eliminates cross-distro tool availability issues. Desktop
packages are downloaded and renamed per format to match the mage
target glob patterns. Also adds --allow-untrusted to apk index
since nfpm-produced .apk packages are unsigned.
2026-04-13 11:19:12 +02:00
kolaente 136fafdf37 fix(ci): install libarchive-tools for repo-add bsdtar dependency
repo-add uses bsdtar to validate packages, which requires
libarchive-tools. The .archlinux extension works fine with repo-add
so the rename to .pkg.tar.zst was unnecessary. Also removes debug
steps.
2026-04-13 10:50:56 +02:00
kolaente 2a2b3c787e fix(ci): add deeper debug for archlinux/pacman package contents 2026-04-13 08:22:18 +02:00
kolaente ab6cdf91eb fix(ci): add debug step to list incoming package files 2026-04-12 19:56:03 +02:00
kolaente e1fed9e252 fix(ci): install makepkg for repo-add utility scripts
repo-add from pacman-package-manager sources scripts from
/usr/share/makepkg/util/ which are shipped in the separate
makepkg package on Ubuntu.
2026-04-12 17:59:32 +02:00
kolaente 80ecaeb567 fix(ci): sign APT Release files manually instead of via reprepro gpgme
reprepro uses gpgme for signing which fails in CI environments because
gpgme cannot access pinentry. Instead, remove SignWith from the reprepro
distributions config and sign Release files manually with gpg after
reprepro finishes, producing both Release.gpg and InRelease.
2026-04-12 17:32:11 +02:00
kolaente e8d12186d1 fix(ci): configure gpg loopback pinentry for reprepro signing
reprepro uses gpgme which bypasses the preset passphrase cache and
tries to launch a pinentry dialog, failing in CI with
"Inappropriate ioctl for device". Adding loopback pinentry mode
allows gpgme to obtain the passphrase without a dialog.
2026-04-12 16:49:36 +02:00
kolaenteandkolaente b375399e34 feat(ci): add publish-repos job for OS package repository metadata
New CI job runs after os-package and desktop jobs complete. Downloads
all package artifacts, runs Mage repo targets to generate repository
metadata (APT, RPM, APK, Pacman), GPG-signs the metadata, and uploads
to R2 under /repos/.

Publishes to stable suite for tagged releases, unstable for main
branch builds. Artifact uploads from os-package and desktop jobs are
no longer gated on tags to support this.
2026-04-12 12:06:14 +00:00
kolaenteandGitHub 1cde0a1705 feat(ci): add multi-architecture support for OS package builds (#2610) 2026-04-12 12:24:08 +02:00
kolaente c92dcf6351 chore(ci): add debugging around release signing 2026-02-08 22:23:23 +01:00