gnilebein/nextcloud-workflow-deck-automation
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 6 Activity

Pin actions/upload-artifact back to v3
Lint info.xml / xml-lint (push) Successful in 15s
Details
Lint PHP / php-lint (8.2) (push) Successful in 42s
Details
Lint PHP / php-lint (8.3) (push) Successful in 43s
Details
Lint PHP / php-lint (8.4) (push) Successful in 41s
Details
PHPUnit / unit-tests (push) Successful in 48s
Details
Build release artifact / package (push) Successful in 1m49s
Details

Browse Source 
v4+ uses the @actions/artifact v2 backend, which this self-hosted
Gitea instance rejects as unsupported since it identifies as GHES to
the action's GHES-detection check. checkout/setup-node don't have
this issue and stay on v7.
This commit is contained in:
Patrick Niebeling
2026-08-13 12:13:52 +02:00
parent d4c75c4942
commit 086c8c06f3
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build-release.yml
+1 -1
View File
@@ -29,7 +29,7 @@ jobs:
- name: Package appstore artifact - name: Package appstore artifact
run: make appstore run: make appstore
- uses: actions/upload-artifact@v7 - uses: actions/upload-artifact@v3
with: with:
name: workflow_deck_automation-${{ gitea.ref_name }} name: workflow_deck_automation-${{ gitea.ref_name }}
path: build/artifacts/appstore/*.tar.gz path: build/artifacts/appstore/*.tar.gz
CLAUDE.md
+2
View File
@@ -51,6 +51,8 @@ There is no meaningful way to test the Deck integration itself outside a real Ne
**If the tagged build fails and no artifact was ever produced**, fix the issue on `main` and *move* the existing tag to the fixed commit instead of bumping to a new version number (`git tag -d vX.Y.Z && git tag -a vX.Y.Z -m "..." && git push origin :refs/tags/vX.Y.Z && git push origin vX.Y.Z`) — this is how `v0.1.0` was handled through several `build-release.yml` fixes before it first built successfully. Once a version has actually produced a published artifact, don't move its tag anymore; bump normally instead. **If the tagged build fails and no artifact was ever produced**, fix the issue on `main` and *move* the existing tag to the fixed commit instead of bumping to a new version number (`git tag -d vX.Y.Z && git tag -a vX.Y.Z -m "..." && git push origin :refs/tags/vX.Y.Z && git push origin vX.Y.Z`) — this is how `v0.1.0` was handled through several `build-release.yml` fixes before it first built successfully. Once a version has actually produced a published artifact, don't move its tag anymore; bump normally instead.
**`actions/upload-artifact` must stay on `@v3`, not `@v4`+.** This self-hosted Gitea instance identifies as GHES to the official `actions/*` JS actions, which refuse to run `@actions/artifact` v2.0.0+ (used internally by `upload-artifact@v4` and later) against GHES: `GHESNotSupportedError`. `actions/checkout` and `actions/setup-node` don't have this problem and can be kept on their latest majors — only the artifact upload/download actions are affected, because they're the ones that talk to a version-specific backend API rather than just running local commands.
## Data flow / architecture map ## Data flow / architecture map
- **UI**: `src/PersonalSettings.vue` (Vue 3, mounted from `templates/settings/personal.php` into the section registered by `lib/Settings/PersonalSection.php` + `lib/Settings/Personal.php`) talks to `lib/Controller/WorkflowController.php` (an `OCSController`) via `src/api.js`, hitting OCS routes declared in `appinfo/routes.php` (`/ocs/v2.php/apps/workflow_deck_automation/api/v1/...`). - **UI**: `src/PersonalSettings.vue` (Vue 3, mounted from `templates/settings/personal.php` into the section registered by `lib/Settings/PersonalSection.php` + `lib/Settings/Personal.php`) talks to `lib/Controller/WorkflowController.php` (an `OCSController`) via `src/api.js`, hitting OCS routes declared in `appinfo/routes.php` (`/ocs/v2.php/apps/workflow_deck_automation/api/v1/...`).