Skip to content

fix(release): tag releases as v1.0.0 - #16

Merged
arosasg merged 1 commit into
mainfrom
fix/release-tag-v1
Oct 29, 2026
Merged

arosasg merged 1 commit into
mainfrom
fix/release-tag-v1

Conversation

@arosasg

@arosasg arosasg commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Problem

release-please tagged the first release didit-java-v1.0.0 (the package name goes into the tag by default). The publish job checks the tag against v<version> (test "v${version}" = "didit-java-v1.0.0"), so run 40877175491 stopped before uploading to Maven Central.

Solution

include-component-in-tag: false in release-please-config.json, so tags are v1.0.0, the format the workflow expects and the other SDKs use (same fix as sdk-php#15).

Verification

  • The workflow's own check compares against v${version}, which this tag format satisfies.
  • After merge, the bad tag and release are removed and release-please re-creates the 1.0.0 release from release PR chore(main): release didit-java 1.0.0 #15.

🤖 Generated with Claude Code

release-please tagged the first release didit-java-v1.0.0 because the package
name is set, and the publish job checks the tag against v<version>, so it
stopped before uploading to Maven Central. include-component-in-tag: false makes
the tag v1.0.0, the format the workflow and the other SDKs use.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@arosasg

arosasg commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

Codex review (codex CLI, account codex-2, model gpt-5.6-sol)


💡 Code review

Reviewed commit: e78fd22

No blocking findings in commit e78fd22.

Verdict: APPROVE

@arosasg
arosasg merged commit d9b1514 into main Oct 29, 2026
11 checks passed
@arosasg
arosasg deleted the fix/release-tag-v1 branch October 29, 2026 12:58
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