Please tag a 3.0.0 release

[thallgren]

It is currently not possible to reference a stable release of gopkg.in/yaml.v3 from a go.mod file. Please tag the v3.0.0 release.

[JulienBreux]

Thanks & Up 😊

[niemeyer]

Sorry for the delay.. I've been on an event for a few days. I'll reserve time to offer go-yaml some more love soon.

[JulienBreux]

@niemeyer No problem, thanks for your time and your brain!

[powerman]

Any update on this?

[mattfarina]

@niemeyer any update?

[niemeyer]

The time is coming. I want to review a few last details before tagging it, but we're close.

[yingzhuivy]

@niemeyer any update on this?

[Hunsin]

What's the main issue that blocks tagging a v3 release?

[stevehipwell]

Any update?

[rr3tt]

Any update on this? Would like to consume v3 if possible.

[ptxmac]

The time is coming. I want to review a few last details before tagging it, but we're close.

This comment is now almost one and a half years old... Could you elaborate on what happened to "a few last details"?

[niemeyer]

Hi @ptxmac

You can see what happened since then in the commit history. I work on go-yaml in batches, and I'll be reserving some time soon to do another push on v3 and tag the release at the end of it, and also switch the default branch off v2.

Sorry for the delay. I can imagine it feels frustrating to be waiting on the other side.

[ptxmac]

Thanks for the reply!

I've been using v3 for a long time and it's been quite stable, so I don't mind waiting. It was more the lack of insight into why it's delayed that's a bit frustrating (Having a milestone with which issues are blocking v3 could help in that regard).

I understand it's basically a one-man project, so it's understandable if more tracking is not realistic :)

[sagikazarmark]

Hey @niemeyer !

Sorry for being yet another person asking about this, but I received a PR in Viper (spf13/viper#1264) upgrading to v3 and I'm not very familiar with its history, so I'm having a hard time making the decision to accept it.

Is v3 considered stable at this point? I'm mostly concerned about breaking changes that in turn would result in breaks in Viper as well. Also, the last commit is from January which could mean that there are no large outstanding tasks.

Do you have a timeline in mind for tagging a new version?

Negative answer for both questions is perfectly fine, I just thought you might have an update for me before I decide what to do with that PR.

Thanks for your work on this project!

[dod38fr]

Looks like version 3.0.1 is out: https://github.com/go-yaml/yaml/releases/tag/v3.0.1

I guess this bug can be closed.