Commit Graph

8 Commits

Author SHA1 Message Date
Ignacio Ballesteros
52efde64c0 fix: mark rolling 'release' as pre-release so v1.0.0 shows as latest
All checks were successful
CI / build (push) Successful in 21s
Release / build (push) Successful in 26s
Release / update-rolling-release (push) Successful in 6s
Release / publish-release (push) Successful in 6s
2026-02-17 23:52:51 +01:00
Ignacio Ballesteros
2768eb39de fix: correct Gitea Actions release workflow
All checks were successful
CI / build (push) Successful in 20s
Release / build (push) Successful in 26s
Release / update-rolling-release (push) Successful in 7s
Release / publish-release (push) Successful in 7s
- Use gitea.ref/server_url/repository context vars instead of GitHub env vars
- Move API_URL and REPO into env: block so context expressions are evaluated
- Pass gitea.ref via env: for version extraction (GITEA_REF)
- Replace grep/cut JSON parsing with jq throughout
- Fix tag creation body: use 'target' key instead of 'message'
- Add set -euo pipefail and diagnostic echo output to both run blocks
- Add null check on jq-parsed RELEASE_ID in publish-release
2026-02-17 23:50:08 +01:00
Ignacio Ballesteros
30f2b4f810 fix: use gitea.token instead of missing GITEA_TOKEN secret
Some checks failed
CI / build (push) Successful in 20s
Release / build (push) Successful in 25s
Release / update-rolling-release (push) Failing after 17s
Release / publish-release (push) Has been skipped
2026-02-17 23:33:53 +01:00
Ignacio Ballesteros
f47a203a80 fix: downgrade artifact actions to v3 for Gitea GHES compatibility
Some checks failed
CI / build (push) Successful in 36s
Release / build (push) Successful in 38s
Release / update-rolling-release (push) Failing after 17s
Release / publish-release (push) Has been skipped
2026-02-17 23:30:00 +01:00
Ignacio Ballesteros
1ed9829f58 ci: add CI workflow for main, fix release pipeline ordering and node version
Some checks failed
CI / build (push) Successful in 45s
Release / build (push) Failing after 22s
Release / update-rolling-release (push) Has been skipped
Release / publish-release (push) Has been skipped
- Add ci.yml to build on every push to main (Node 22)
- Add job-level guard on release build job (startsWith refs/tags/v)
- Bump Node to 22 in release.yml to satisfy zotero-plugin-scaffold >=22.8.0
- Extract publish-release as a third job (needs: [build, update-rolling-release])
  so the versioned release and XPI are only published after the full pipeline succeeds
2026-02-17 23:24:05 +01:00
Ignacio Ballesteros
e836809fc0 fix: use GITEA_SERVER_URL instead of GITHUB_SERVER_URL in release workflow 2026-02-17 23:03:27 +01:00
Ignacio Ballesteros
3b24386dd0 ci: add rolling 'release' tag job to keep update.json current
Some checks failed
Release / build (push) Failing after 1m38s
Release / update-rolling-release (push) Has been skipped
Add a second CI job that runs after the versioned release is published.
It upserts a permanent Gitea release tagged 'release', replacing its
assets with the freshly built update.json and update-beta.json.
This is the URL Zotero polls for auto-update checks per manifest.json.
2026-02-17 22:45:39 +01:00
Ignacio Ballesteros
70f7fac23e chore: initial project commit 2026-02-17 21:25:46 +01:00