Skip to content

ci(release): bump shared pipeline to v3#183

Merged
chhoumann merged 1 commit into
masterfrom
ci/release-pipeline-v3
Jul 11, 2026
Merged

ci(release): bump shared pipeline to v3#183
chhoumann merged 1 commit into
masterfrom
ci/release-pipeline-v3

Conversation

@chhoumann

Copy link
Copy Markdown
Owner

What

Bumps the shared release-pipeline pins in the three release caller stubs
(release-prepare.yml, release-trigger.yml, release.yml) from v2 to the
new v3 tag of
chhoumann/obsidian-plugin-workflows
(v3 = 8471ad7827fcee306ac2b8c10e984e57aeefe7df).

Why - what v3 brings

  • feat!: stop cutting releases for chore-only commits
  • fix: handle bare release merge subjects
  • fix: retry the tag-verify read after createRef, closing the tag-verify
    replication race that hit 2 of the first 3 production releases

Behavior change

A commit range containing only chore commits will no longer produce a standing
release PR. This is intended - see
chhoumann/obsidian-plugin-workflows#4.

Validation

  • YAML parses (PyYAML safe_load)
  • actionlint clean on all three stubs

The ci / codeql / dependency-review / pr-title callers pin @v1 (advanced
in place) and are intentionally left unchanged.

Point the release-prepare/trigger/release caller stubs at the new v3 tag
of chhoumann/obsidian-plugin-workflows. v3 brings three changes:

- feat!: stop cutting releases for chore-only commits
- fix: handle bare release merge subjects
- fix: retry the tag-verify read after createRef, closing the
  replication race that hit 2 of the first 3 production releases

Note the breaking change: a commit range containing only chore commits
will no longer produce a standing release PR (intended behavior, see
chhoumann/obsidian-plugin-workflows#4).
@chhoumann chhoumann merged commit 1d1a33d into master Jul 11, 2026
8 checks passed
@chhoumann chhoumann deleted the ci/release-pipeline-v3 branch July 11, 2026 15:41
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