Skip to content

build(deploy): added ability to perform content only deploy #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kieronlanning merged 1 commit into from
Sep 21, 2026
Merged

build(deploy): added ability to perform content only deploy #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ name: Release
on:
push:
branches: [main]
paths:
- package.json

# Serialize releases; the reusable workflow skips when the v{version} tag already exists.
concurrency:
Expand Down
9 changes: 7 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,8 +272,9 @@ asset checks, the production build, link crawl, generated-output checks, and
built-output tests. Releasing means bumping `version` in the root
`package.json` and merging: the `Release` workflow (`purview-release.yml`,
`release-mode: GitHubRelease`) runs the pipeline, tags `v{version}`, and uploads
the built `dist/` zip as a GitHub release asset. `deploy.yml` continues to
publish the site to GitHub Pages.
the built `dist/` zip as a GitHub release asset. Content-only updates do not
need a version bump; they are handled by `deploy.yml`, which republishes the
site to GitHub Pages from the latest synced data.

## GitHub Pages deployment

Expand Down Expand Up @@ -321,6 +322,10 @@ The deploy workflow listens for `repository_dispatch` with type
`purview-site-rebuild`. The payload is informational and is not required for
the rebuild to succeed; the build always fetches fresh data itself.

The release workflow is intentionally scoped to root `package.json` changes so
content refreshes do not get blocked by an unchanged version or an existing
`v{version}` tag.

## Dependency maintenance

Dependabot (`.github/dependabot.yml`) keeps Bun dependencies and GitHub Actions
Expand Down
Loading