Skip to content

fix: don't attempt a git commit on a plugin's first-ever release - #4

Merged
nielsweistra merged 1 commit into
mainfrom
fix/first-release-no-commit
Aug 14, 2026
Merged

fix: don't attempt a git commit on a plugin's first-ever release#4
nielsweistra merged 1 commit into
mainfrom
fix/first-release-no-commit

Conversation

@nielsweistra

Copy link
Copy Markdown
Member

On a first release (no prior tag), the script wrote the plugin's CURRENT version back into plugin.json unchanged, producing zero diff — git commit then failed with "nothing to commit", exit 1.

Caught by live testing: hello-plugin's first publish run in ITlusions/ITL.Claude.PluginMarketplace failed exactly here. Now the node-write/commit/push only happens on an actual version bump; the first-release path tags HEAD directly without touching plugin.json.

🤖 Generated with Claude Code

On a first release (no prior tag), the script wrote the plugin's CURRENT
version back into plugin.json unchanged, producing zero diff — 'git
commit' then failed with 'nothing to commit, working tree clean',
exit 1. Caught by live testing: hello-plugin's first publish run failed
here. Now only the node-write/commit/push happens on an actual bump;
the first-release path just tags HEAD directly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@nielsweistra
nielsweistra merged commit f92d091 into main Aug 14, 2026
4 checks passed
@nielsweistra
nielsweistra deleted the fix/first-release-no-commit branch August 14, 2026 02:01
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