Skip to content

Commit 86191dc

Browse files
committed
docs: clarify create-linked-release tagging strategy in README
1 parent b2fd23e commit 86191dc

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -357,7 +357,7 @@ a GitHub repository using a treeless, sparse clone workflow.
357357

358358
This repo publishes container images to GitHub Container Registry from version tags.
359359

360-
- `create-linked-release.yml` checks the latest matching upstream release on a schedule and creates a local tag when a new one appears
360+
- `create-linked-release.yml` checks the latest matching upstream release per major (`groupBy=major`) on a schedule: the latest v1.x release is tagged at the head of the `v1` branch and every newer major gets its own tag at the head of `master` (existing tags are never moved)
361361
- `build-and-deploy.yml` runs on `v*` tags, validates semver, and publishes the image to `ghcr.io/ophiosdev/opencode-cli`
362362
- Published tags include semver variants, a commit SHA tag, and `latest` when enabled for the default branch
363363

0 commit comments

Comments
 (0)