Skip to content

fix(strategy): keep release tags by default - #49

Merged
noctuum merged 1 commit into
mainfrom
default-tag-filter
Oct 21, 2026
Merged

noctuum merged 1 commit into
mainfrom
default-tag-filter

Conversation

@noctuum

@noctuum noctuum commented Oct 21, 2026

Copy link
Copy Markdown
Member

Without tag_pattern, and for github-tag also without tag_version_regex, github-tag, gitlab-tag and gitea-tag keep only the tags of the form v1.2.3 or 1.2.3. Before, sort -V put a tag named latest or v2.1.0-rc1 above every release, and the package stopped updating. When no tag has that form, the check fails with a message that names the fields to set. release_tags in scripts/lib.sh holds the filter.

docs/WORKFLOW.md, docs/SUPPORTED-PACKAGES.md and packages/example.yml.sample describe the default. The examples use release-* instead of v*, which lets pre-release tags through.

Without tag_pattern, the tag strategies take only v1.2.3 and 1.2.3.
@codecov

codecov Bot commented Oct 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@noctuum
noctuum merged commit 2c2f2eb into main Oct 21, 2026
5 checks passed
@noctuum
noctuum deleted the default-tag-filter branch October 21, 2026 01:07
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