v3.0.78 release tag applied to master (2.x) branch instead of 3.0.0 branch

git show で refs/tags/v3.0.78 を調査し、origin/3.0.0 上のリリース準備用コミット、特に 1a779509 と 4c588898 と比較します。tag が 2.x の master commit ではなく 3.x の release を指していることを確認し、その後 Homebrew のメンテナーに連絡して formula を更新できるようにします。

Issue: v3.0.78 release tag applied to master (2.x) branch instead of 3.0.0 branch

Bug description

The v3.0.78 git tag is applied to a commit on the master branch (the 2.x codebase)
instead of the 3.0.0 branch (the 3.x codebase).

Evidence

The tagged commit is a routine 2.x dependency update on master:

$ git show refs/tags/v3.0.78 --stat
commit 70cf625cbea6d813f24adbfc422eef9ecd23656e
Author: robert-hebel-sb <robert.hebel@smartbear.com>
Date:   Mon Dec 29 17:02:31 2025 +0100

    chore(deps): update vulnerable validator & js-yaml (#12659)

Building the CLI JAR from this tag produces a 2.x artefact:

Main-Class: io.swagger.codegen.SwaggerCodegen   ← 2.x namespace
implementation-version: 2.4.51-SNAPSHOT         ← 2.x version

The correct 3.x namespace would be io.swagger.codegen.v3.SwaggerCodegen.

Meanwhile, the 3.0.0 branch has the 3.0.78 release prepared but untagged:

$ git log origin/3.0.0 --oneline | head -4
30d353d chore: bump snapshot to 3.0.79-SNAPSHOT
7aed624 chore: update microdnf before install
1a779509 chore: prepare release 3.0.78
4c588898 chore: prepare release 3.0.78

Impact

The Homebrew formula for swagger-codegen packages the JAR built from the v3.0.78 tag.
Users who install via Homebrew receive a 2.x binary despite the formula advertising 3.0.78:

$ brew install swagger-codegen
$ swagger-codegen version
2.4.51-SNAPSHOT

Any tooling that relies on git ls-remote --tags to find the latest v3.* release will
also pick up this tag and unknowingly build/use 2.x code.

Suggested fix

Move (or re-create) the v3.0.78 tag to point to the "prepare release 3.0.78" commit
on the 3.0.0 branch (1a779509 or 4c5888986), and notify the Homebrew maintainers
so the formula can be updated.