Build error after upgrading to v0.8.2

[richardsliu]

Looks like v0.8.0 release was moved recently. I've tried upgrading my dependencies to v0.8.2, but I am getting this error:

go: finding github.com/kubernetes-sigs/application/api/v1beta1 latest
go: finding github.com/kubernetes-sigs/application/api latest
go: github.com/kubernetes-sigs/application@v0.8.2: parsing go.mod: unexpected module path "sigs.k8s.io/application"
go: error loading module requirements

Anyone else seeing this?

[Jeffwan]

v0.8.1 failed as well.

$ go get github.com/kubernetes-sigs/application@v0.8.1
go: finding github.com/kubernetes-sigs/application v0.8.1
go: downloading github.com/kubernetes-sigs/application v0.8.1
verifying github.com/kubernetes-sigs/application@v0.8.1: checksum mismatch
    downloaded: h1:2vVgBheRdYZtP78Tda0MEWL3NKwSDynvG/8/Wz1clE4=
    sum.golang.org: h1:tnIN+iijr0kDJxvOhnqjoXV+3hWydRNy8OHisMyO71U=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

[Jeffwan]

@barney-s Can you help take a look?

[tmarcu]

It looks like both tags were just updated, which now gives a repo with different structure than before. The import path for 0.8.1 is no longer valid

module github.com/kubernetes-sigs/application@latest (v0.8.2) found, but does not contain package github.com/kubernetes-sigs/application/pkg/apis/app/v1beta1

This is with using a replace in go.mod like so:

replace github.com/kubernetes-sigs/application => sigs.k8s.io/application v0.8.1

to get past the hash & incorrect module name errors.

[barney-s]

@Jeffwan - Did @tmarcu suggestion help ?

[Jeffwan]

@Jeffwan - Did @tmarcu suggestion help ?

It works. My suggestion is make tags immutable... It's fine to cut a tags, otherwise it breaks project has dependency on it

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/application/issues/190#issuecomment-706390600): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.