SDK versioning number incorrect - unable to target latest Go package version

[SamuelDev]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe the bug

#447 The PR that generated version 2.5.0 was closed and the bot directly committed the file for the next release with the wrong versioning number.

https://github.com/ory/sdk/blob/master/spec/hydra/v25.4.0.json was created and merged making it impossible to version 2.5.0 in Go due to the semantics of Go packages.

Reproducing the bug

1. Create new Go project
2. Attempt to add the Hydra SDK package with get github.com/ory/hydra-client-go/v2@v25.4.0
3. Observe failure

You can also run go list -m -versions -mod=mod github.com/ory/hydra-client-go/v2 and observe no new package being listed past 2.4.0-alpha.1

Relevant log output

go get github.com/ory/hydra-client-go/v2@v25.4.0

go: github.com/ory/hydra-client-go/v2@v25.4.0
: invalid version: module path includes a major version suffix, so major version must match

Relevant configuration

Version

2.3.0

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

No response

[SamuelDev]

pinging you @adamwalach as you might be trying to fix this currently? Is this a known issue already?

[vinckr]

see here
ory/hydra-client-go#28
and
ory/hydra-client-go#29

[pi-kei]

Clients for keto and kratos (ory/keto-client-go and ory/kratos-client-go) are also must be regenerated the same as hydra client. go get with specified version @v25.4.0 requires a module name to end with /v25.

[vinckr]

Clients for keto and kratos (ory/keto-client-go and ory/kratos-client-go) are also must be regenerated the same as hydra client. go get with specified version @v25.4.0 requires a module name to end with /v25.

It should have been fixed here #450 - not sure myself but I asked a colleague to take a look