Problem
The Foundry Local website models page has CLI download links hardcoded to the old cli-preview-0.10.0 release.
Page:
https://www.foundrylocal.ai/models
Old link target:
https://github.com/microsoft/Foundry-Local/releases/tag/cli-preview-0.10.0
This can send users to an outdated CLI after newer preview releases are published.
Proposed solution
The website should not hardcode a specific CLI preview release tag.
Instead, it should resolve the latest cli-preview-* GitHub release at build/server time, generate platform-specific CLI links from that release's assets, and fall back to the general Foundry Local releases page if release discovery fails.
Expected behavior:
Follow-up requirement
After publishing a new CLI preview release, the release pipeline should trigger a website/Vercel redeploy so the build-time resolver refreshes immediately.
Problem
The Foundry Local website models page has CLI download links hardcoded to the old
cli-preview-0.10.0release.Page:
https://www.foundrylocal.ai/models
Old link target:
https://github.com/microsoft/Foundry-Local/releases/tag/cli-preview-0.10.0
This can send users to an outdated CLI after newer preview releases are published.
Proposed solution
The website should not hardcode a specific CLI preview release tag.
Instead, it should resolve the latest
cli-preview-*GitHub release at build/server time, generate platform-specific CLI links from that release's assets, and fall back to the general Foundry Local releases page if release discovery fails.Expected behavior:
Follow-up requirement
After publishing a new CLI preview release, the release pipeline should trigger a website/Vercel redeploy so the build-time resolver refreshes immediately.