Skip to content

fix(scripts): tag each module on its latest commit - #1184

Merged
matifali merged 4 commits into
mainfrom
fix/tag-release-latest-commit
Oct 22, 2026
Merged

matifali merged 4 commits into
mainfrom
fix/tag-release-latest-commit

Conversation

@matifali

Copy link
Copy Markdown
Member

Description

#1168 made tag_release.sh tag the commit that first introduced a module's current README version. A later commit that changes the module without bumping the version (e.g. #1182 on agent-relay-cursor, still 0.5.0) was then left out of the tag.

The script now tags the newest first-parent commit that touched the module directory. Since the README version at HEAD is the version being tagged, that commit always carries it. Shallow clones still fall back to HEAD with a warning.

MAINTAINER.md updated to match.


Generated with Claude Code using Claude Sonnet 5.5

@matifali
matifali requested a review from dluman October 22, 2026 15:13
@matifali
matifali enabled auto-merge (squash) October 22, 2026 15:14
@matifali
matifali disabled auto-merge October 22, 2026 15:15
@matifali
matifali merged commit 0d7ec75 into main Oct 22, 2026
4 checks passed
@matifali
matifali deleted the fix/tag-release-latest-commit branch October 22, 2026 15:17
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.

3 participants