Skip to content

chore: sync changes from the upstream template #427

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
devantler merged 1 commit into from
Oct 19, 2026
Merged

chore: sync changes from the upstream template #427

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
8 changes: 7 additions & 1 deletion docs/REFERENCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,13 @@ code owners, so template-sync never overwrites it.

In generated tenant repositories with the required App setup, `release.yaml`
uses eligible Conventional-Commit merges to `main` to decide whether to create
`vX.Y.Z` tags. It deliberately no-ops in this upstream template.
`vX.Y.Z` tags. It deliberately no-ops in this upstream template. `.releaserc`
cuts a release for `feat`, `fix`, `perf`, breaking and `build(deps)` commits;
`build(deps)` is Dependabot's prefix for runtime packages and the Docker base
image, so their updates reach production on their own. GitHub Actions updates
use the `ci` prefix (set in `.github/dependabot.yml`) and release nothing.
Tenants own both files, so an existing tenant adds the `build(deps)` rule and
the `ci` prefix itself.
Each tag triggers `cd.yaml`, which calls the platform's
[`publish-app.yaml`](https://github.com/devantler-tech/actions/blob/main/.github/workflows/publish-app.yaml)
reusable workflow to build the image, **pin its digest into
Expand Down
Loading