If we now take a look at the Hash, which is the commit hash referenced:
v1.0.0: 553261d24be7d22d76251fae0cd85bb51be9bb9d:
❯ git show 553261d24be7d22d76251fae0cd85bb51be9bb9d
commit 553261d24be7d22d76251fae0cd85bb51be9bb9d
Merge: 1ef2441 1d51c28
Author: zhengxiexie <xizheng@vmware.com>
Date: Mon Oct 30 13:13:15 2023 +0800
Merge pull request #288 from zhengxiexie/codegen_alpha2_vpc_dev
Support codegen for v1alpha2
v0.1.0: 1269a61ff22c969923f260553d7961803e53f63e
❯ git show 1269a61ff22c969923f260553d7961803e53f63e
commit 1269a61ff22c969923f260553d7961803e53f63e (tag: pkg/apis/v0.1.0)
Author: XiaoPei Liu <lxiaopei@lxiaopei05N6R.vmware.com>
Date: Fri Dec 22 10:02:17 2023 +0800
Change pkg/apis and pkg/client in go.mod
In go.mod, change to use local pkg/apis and pkg/client.
We can see v1.0.0 is actually older. Also that commit only exists on the vpc_dev branch, not on main.
I wanted to know where this came from, if there maybe was a push of a v1.0.0 tag by accident?
Dependabot opened a bump PR for:
I wanted to take a look at the diff and realised the repo does not have a
v1.0.0
tag orpkg/apis/v1.0.0
.Taking a look at how go resolves this:
for v1.0.0:
for v0.1.0
If we now take a look at the
Hash
, which is the commit hash referenced:v1.0.0
:553261d24be7d22d76251fae0cd85bb51be9bb9d
:v0.1.0
:1269a61ff22c969923f260553d7961803e53f63e
We can see
v1.0.0
is actually older. Also that commit only exists on thevpc_dev
branch, not on main.I wanted to know where this came from, if there maybe was a push of a v1.0.0 tag by accident?