manifest.json points at private cgg archives -> 404 for external users #3

Open
opened 2026-10-05 05:13:28 +00:00 by justin · 0 comments
Owner

Summary

manifest.json points every workbench at cgg/<repo>/archive/main.zip. Those four repositories are private, so the updater can fetch the manifest but then 404s on every download for any user without a CITFJ account. The repository itself is now public (comfac-dist/ComfacCAD), so the manifest is the remaining blocker.

Evidence (anonymous)

URL Result
cgg/Comfac-2D/archive/main.zip 404
cgg/Comfac-Archi_Tools/archive/main.zip 404
cgg/Comfac-cadassets/archive/main.zip 404
cgg/Comfac-MEP_Tools/archive/main.zip 404
comfac-dist/ComfacCAD/releases/download/v1.0.0/Comfac-2D.zip 200

Change

Repoint each download_url at the corresponding asset on the public release v1.0.0, which carries the four workbenches as unmodified main archives (preserving the single root wrapper folder that download_and_extract_wb() requires).

Source repositories stay private — only the built archives are published.

Why pinned tag URLs, not latest

Verified against this instance (Forgejo 13.0.5): releases/latest/download/<asset> returns 404. It is not supported, so the manifest must reference the tag explicitly. Consequence: cutting a new bundle release requires a manifest commit to bump the tag. That is by design here — it keeps a published manifest from silently changing under an existing install.

Acceptance criteria

  • Anonymous fetch of manifest.json returns 200
  • All four download_url values return 200 anonymously
  • Updater deploys all four workbenches on a clean install with no CITFJ account
  • Depends on #1 (the manifest URL must resolve before any of this is reached)
## Summary `manifest.json` points every workbench at `cgg/<repo>/archive/main.zip`. Those four repositories are **private**, so the updater can fetch the manifest but then **404s on every download** for any user without a CITFJ account. The repository itself is now public (`comfac-dist/ComfacCAD`), so the manifest is the remaining blocker. ## Evidence (anonymous) | URL | Result | |---|---| | `cgg/Comfac-2D/archive/main.zip` | 404 | | `cgg/Comfac-Archi_Tools/archive/main.zip` | 404 | | `cgg/Comfac-cadassets/archive/main.zip` | 404 | | `cgg/Comfac-MEP_Tools/archive/main.zip` | 404 | | `comfac-dist/ComfacCAD/releases/download/v1.0.0/Comfac-2D.zip` | **200** | ## Change Repoint each `download_url` at the corresponding asset on the public release **v1.0.0**, which carries the four workbenches as unmodified `main` archives (preserving the single root wrapper folder that `download_and_extract_wb()` requires). Source repositories **stay private** — only the built archives are published. ## Why pinned tag URLs, not `latest` Verified against this instance (Forgejo 13.0.5): `releases/latest/download/<asset>` returns **404**. It is not supported, so the manifest must reference the tag explicitly. Consequence: **cutting a new bundle release requires a manifest commit to bump the tag.** That is by design here — it keeps a published manifest from silently changing under an existing install. ## Acceptance criteria - [ ] Anonymous fetch of `manifest.json` returns 200 - [ ] All four `download_url` values return 200 anonymously - [ ] Updater deploys all four workbenches on a clean install with no CITFJ account ## Related - Depends on #1 (the manifest URL must resolve before any of this is reached)
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
comfac-dist/ComfacCAD#3
No description provided.