Bump version to 0.5.2

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fix CI: use PACKAGE_TOKEN for package registry operations
2026-03-01 17:28:20 -05:00 · 2026-03-01 17:23:13 -05:00
2 changed files with 2 additions and 2 deletions
--- a/.forgejo/workflows/release.yml
+++ b/.forgejo/workflows/release.yml
@ -207,7 +207,7 @@ jobs:
      - name: Publish latest.json to package registry
        env:
-          FORGEJO_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          FORGEJO_TOKEN: ${{ secrets.PACKAGE_TOKEN }}
        run: |
          # DELETE uses API v1, PUT uses the package upload API
          DELETE_URL="${GITHUB_SERVER_URL}/api/v1/packages/${GITHUB_REPOSITORY_OWNER}/generic/simpl-resultat/latest"
--- a/src-tauri/tauri.conf.json
+++ b/src-tauri/tauri.conf.json
@ -1,7 +1,7 @@
 {
  "$schema": "https://schema.tauri.app/config/2",
  "productName": "Simpl Resultat",
-  "version": "0.5.1",
+  "version": "0.5.2",
  "identifier": "com.simpl.resultat",
  "build": {
    "beforeDevCommand": "npm run dev",
Author	SHA1	Message	Date
le king fu	079ddfb0e7	Bump version to 0.5.2 All checks were successful Release / build-and-release (push) Successful in 26m18s Details Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-01 17:28:20 -05:00
le king fu	fc906d6d55	Fix CI: use PACKAGE_TOKEN for package registry operations The automatic GITHUB_TOKEN does not have package permissions in Forgejo. Use a dedicated PACKAGE_TOKEN secret with the package scope instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-01 17:23:13 -05:00