Latest v1.x tag doesn't point to a commit in the repo, previous version got retracted

[philippgille]

Hallo 👋 , I was checking a Dependabot PR for a bump from v1.74.6 to v1.74.8, and noticed the latter one is a tag on a commit that doesn't exist in the repo:

---

Then I saw that v1.74.7 is the latest v1.74.x release and also supposed to be the last v1.x release ever (according to the release notes), but it got retracted. v1.74.8 doesn't have a release.

=> Do you plan to tag a v1.74.9 that points to a commit in the repo and publish a release for it? Or if not: What are users of the v1.x version advised to do?

[darccio]

@philippgille The whole v1.74.x release branch is expected to be the last v1 release ever. The note in release notes is present in all the releases, that has been done as a convenient way to push adoption of github.com/DataDog/dd-trace-go/v2. The whole v1 version will be deprecated EOY.

v1.74.x users should be able to use v1.74.8 even if it's not pointing to a commit in the repository. It's still a valid release. We might consider tagging a last v1.74.9 if this situation might cause any issue or concerns.

Our recommendation is to migrate to github.com/DataDog/dd-trace-go/v2 using our migration guide.

[philippgille]

Thanks for the reply!

The whole v1.74.x release branch is expected to be the last v1 release ever.

Yes that's clear.

But the release said specifically that v1.74.7 is the latest release, so when seeing the v1.74.8 tag and then also seeing that it's a commit that's not part of the repo, and also seeing there's no GitHub release for it, so also no changelog, it seems a bit messy and makes you wonder if there was another mistake and the .8 is maybe not supposed to be used.

v1.74.x users should be able to use v1.74.8 even if it's not pointing to a commit in the repository. It's still a valid release.

Thanks for clarifying that it can be used!

Can you please explain why the commit is not part of the repo and why is there no GitHub release for it? Is that by accident, or was there some issue with the commit, or some other reason?