Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't install latest go client #18795

Closed
akkie opened this issue May 24, 2024 · 3 comments
Closed

Can't install latest go client #18795

akkie opened this issue May 24, 2024 · 3 comments
Assignees
Labels
component/zeebe Related to the Zeebe component/team kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.

Comments

@akkie
Copy link

akkie commented May 24, 2024

Description

It's not possible to install the latest go client.

Steps to reproduce:

go mod init example/hello
go get github.com/camunda/camunda/clients/go/v8

Output:

go: downloading github.com/camunda/camunda v0.0.0-20240524071313-2c67cd01f665
go: downloading github.com/camunda/camunda/clients/go v1.3.14
go: downloading github.com/camunda/camunda/clients/go/v8 v8.5.1
go: github.com/camunda/camunda/clients/go/v8@upgrade (v8.5.1) requires github.com/camunda/camunda/clients/go/v8@v8.5.1: parsing go.mod:
	module declares its path as: github.com/camunda/zeebe/clients/go/v8
	        but was required as: github.com/camunda/camunda/clients/go/v8
@akkie akkie added component/zeebe Related to the Zeebe component/team kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. labels May 24, 2024
@Zelldon
Copy link
Member

Zelldon commented May 24, 2024

Thanks @akkie please still use the old module name. Even when the renaming is already done, just realized that the modules are still available under the old name (which makes sense, as they have been released with that name). This means a module with the new name will be released as soon we create a new tag/release.

Update:

I was able to reproduce this also with the old module names.

$ go get github.com/camunda/zeebe/clients/go/v8@v8.4.2
$ cat go.mod 
module github.com/zeebe-io/test-go

go 1.20

require github.com/camunda/zeebe/clients/go/v8 v8.4.2
$ cat main.go 
package main

import zeebe "github.com/camunda/zeebe/clients/go/v8"

func main() {
	zeebe.Client
}
$ go run main.go 
main.go:3:8: no required module provides package github.com/camunda/zeebe/clients/go/v8; to add it:
	go get github.com/camunda/zeebe/clients/go/v8

It is a problem we are currently look into.

@npepinpe npepinpe self-assigned this May 27, 2024
@npepinpe
Copy link
Member

@Zelldon I'm assigning to you as you're already working on this.

@npepinpe npepinpe assigned Zelldon and unassigned npepinpe May 27, 2024
@Zelldon
Copy link
Member

Zelldon commented May 27, 2024

Hey @akkie

sorry for the confusion around the module name change. I have investigated this further, and realized that this is actually not an issue.

What you have to do is to still use the old module name, like go get github.com/camunda/zeebe/clients/go/v8@v8.5.1

As GitHub will resolve the old name (via redirects), and the old tags/version still contain the old module name. In this regard nothing has changed for now. On new released versions you have to use the new module name, but until a release is out you can keep the old module name.

I hope this helps.

@Zelldon Zelldon closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/zeebe Related to the Zeebe component/team kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
Projects
None yet
Development

No branches or pull requests

3 participants