Skip to content

Rebuild the website when a release is published - #11

Merged
marcellosso merged 1 commit into
mainfrom
site/rebuild-on-release
Oct 22, 2026
Merged

marcellosso merged 1 commit into
mainfrom
site/rebuild-on-release

Conversation

@marcellosso

Copy link
Copy Markdown
Owner

What and why

The website's download buttons read the latest release when the site is built. Vercel only builds on pushes to main, so after v0.1.0 was published the live site still had the build from before it, and every button went to the Releases page.

The Site workflow now also runs when a release is published and calls Vercel's deploy hook (VERCEL_DEPLOY_HOOK secret), so the site is rebuilt with the new release's files. Without the secret it warns and does nothing. The comment in release.ts said this already happened; now it does.

How I checked it

  • pnpm build in site/ with v0.1.0 published: the buttons and install steps link to releases/download/v0.1.0/… for the DMG, the setup .exe, the .deb, the .rpm and the AppImage.
  • The release trigger runs on the next published release.

Left out

Creating the deploy hook in Vercel and storing it as the VERCEL_DEPLOY_HOOK secret is done by hand.

@vercel

vercel Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
localhost-web Ready Ready Preview Oct 22, 2026 9:27pm UTC

@marcellosso
marcellosso merged commit 21bd80b into main Oct 22, 2026
8 checks passed
@marcellosso
marcellosso deleted the site/rebuild-on-release branch October 22, 2026 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant