TDLMPack does not Maven-resolve or download HMCL today — only a README repo link. This PR adds launcher binary publish (Release + generic tdlm-hmcl/latest) and points the client fileApi default at the CDN.
fileApi (HMC-15)
Default is now:
https://packages.dandanton.com/tdlm-client/latest
(Same relative package path as Gitea generic …/tdlm-client/latest; CDN root is https://packages.dandanton.com.)
TDLMPack: set Actions var TDLM_CLIENT_FILE_API=https://packages.dandanton.com/tdlm-client/latest
so server-manifest.json embeds the CDN.
Publish caveat: Pack currently PUTs to TDLM_CLIENT_FILE_API. Either mirror Gitea → CDN, or make CDN accept Pack PUTs — do not leave HMCL on CDN while Pack only writes Gitea without a sync.
See docs/TDLM_CONSUME.md. After merge: ensure TDLM_PACK_TOKEN, run Publish TDLM launcher. No UI changes.
## Summary
TDLMPack does **not** Maven-resolve or download HMCL today — only a README repo link. This PR adds launcher binary publish (Release + generic `tdlm-hmcl/latest`) and points the client **fileApi** default at the CDN.
## fileApi (HMC-15)
Default is now:
`https://packages.dandanton.com/tdlm-client/latest`
(Same relative package path as Gitea generic `…/tdlm-client/latest`; CDN root is `https://packages.dandanton.com`.)
**TDLMPack:** set Actions var
`TDLM_CLIENT_FILE_API=https://packages.dandanton.com/tdlm-client/latest`
so `server-manifest.json` embeds the CDN.
**Publish caveat:** Pack currently PUTs to `TDLM_CLIENT_FILE_API`. Either mirror Gitea → CDN, or make CDN accept Pack PUTs — do not leave HMCL on CDN while Pack only writes Gitea without a sync.
## Launcher consume path
Stable:
- `https://git.nest.potatolab.uk:8443/api/packages/TDLM/generic/tdlm-hmcl/latest/HMCL.exe`
- `…/HMCL.jar`
Versioned: `https://git.potatolab.uk/TDLM/HMCL/releases/latest`
See `docs/TDLM_CONSUME.md`. After merge: ensure `TDLM_PACK_TOKEN`, run **Publish TDLM launcher**. No UI changes.
Add a TDLMPack-oriented publish workflow (nest API, same pattern as
TDLMPack pack.yml) plus docs for the exact consume URLs. Pack builds
still do not Maven-resolve the launcher.
Keep secrets.TDLM_PACK_TOKEN (same name as pack.yml); document that it
is currently a TDLMPack repo secret while MAVEN_* are org-level.
Fall back to github.token so release can proceed after merge without a
new HMCL-only secret when the pack token is promoted or unavailable.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
TDLMPack does not Maven-resolve or download HMCL today — only a README repo link. This PR adds launcher binary publish (Release + generic
tdlm-hmcl/latest) and points the client fileApi default at the CDN.fileApi (HMC-15)
Default is now:
https://packages.dandanton.com/tdlm-client/latest(Same relative package path as Gitea generic
…/tdlm-client/latest; CDN root ishttps://packages.dandanton.com.)TDLMPack: set Actions var
TDLM_CLIENT_FILE_API=https://packages.dandanton.com/tdlm-client/latestso
server-manifest.jsonembeds the CDN.Publish caveat: Pack currently PUTs to
TDLM_CLIENT_FILE_API. Either mirror Gitea → CDN, or make CDN accept Pack PUTs — do not leave HMCL on CDN while Pack only writes Gitea without a sync.Launcher consume path
Stable:
https://git.nest.potatolab.uk:8443/api/packages/TDLM/generic/tdlm-hmcl/latest/HMCL.exe…/HMCL.jarVersioned:
https://git.potatolab.uk/TDLM/HMCL/releases/latestSee
docs/TDLM_CONSUME.md. After merge: ensureTDLM_PACK_TOKEN, run Publish TDLM launcher. No UI changes.466d5e93f5tod9c1e66f03d9c1e66f03to95111d2f84