Skip to main content
Version: Next 🚧

Releasing Website

Release Process​

1. Preparing for Release​

a. The site is not versioned, so there is no version to bump and no tag to push. A release here is simply a merge to main.

b. Content lives in src/content/ and src/pages/ as MDX. Layout and components are in src/layouts/ and src/components/, and the shared component library comes from @krumio/trailhand-ui.

c. Run yarn lint and yarn build locally before opening the PR.

2. Reviewing the PR​

a. The PR will kick off a build and preview, once the preview is available check for relevant changes.

3. Publishing​

a. Merge to main. That triggers Deploy to GitHub Pages (deploy.yaml), which can also be run manually from the Actions tab.

b. The build job checks out the repo and hands off to withastro/action@v6, which installs dependencies, runs the Astro build, and uploads the site as a Pages artifact. It needs two secrets at build time: PUBLIC_RECAPTCHA_SITE_KEY and PUBLIC_API_URL.

c. The deploy job runs after build and publishes the artifact with actions/deploy-pages@v5 into the github-pages environment, which serves epinio.io.

4. Post Release Tasking​

a. Load the site and check the pages you changed. Since nothing validated the build before merge, the deploy run is the first real signal.

b. Triage Dependabot. It runs daily for npm and github-actions, but its PRs get no CI, so each one needs a local build to verify. Note that PRs predating the Astro rewrite may bump packages that are no longer in package.json and can simply be closed.

c. Its important to close out or update any public GitHub issues that were resolved as part of the release, and clean up branches.