Launching yaml/go-yaml

[ingydotnet]

This project started on April 22nd, 2025 when @ingydotnet found out that https://github.com/go-yaml/yaml had been archived.
Ingy reached out to a number of people including go-yaml's author @niemeyer and the people who now are on the @yaml org's go-yaml team.

The project has legs now but there are still a number of things that need to happen before it can be used reliably.
These things will be listed here and should come together by early June (or sooner).

[ingydotnet]

To Do

• Update README with a top STATUS section, to let everyone know more clearly what the plans are.
• Host the vanity domain URLs go.yaml.in/yaml/v3 and /v2.
  • Currently stuck on this. See Requesting help getting the go.yaml.in/yaml.v3 and go.yaml/in/yaml.v2 vanity domain URLs working #12 for details.
• Update go.mod with new vanity domain URL
• Cut new release tags for v3 and v2 branches, and update vanities
• Work the @dims to get https://github.com/kubernetes-sigs/yaml depending on go.yaml.in
• Work with @mattfarina and helm team to get https://github.com/helm/helm depending on go.yaml.in
• Watch for any breakage in downstreams
• Announce the launch of https://github.com/yaml/go-yaml/ as the actively maintained repo
• Ask @niemeyer to link to us from https://github.com/go-yaml/yaml/blob/v3/README.md (Add notice to original repo #20)

[andig]

Kindly ask @niemeyer to close or answer go-yaml/yaml#1072

[andig]

@ingydotnet seems go.mod is done but vanity redirects still not working.

[ingydotnet]

Resolved

[andig]

Friendly ping @niemeyer regarding mentioning this library

[ingydotnet]

What is the best way to announce this?

[dolmen]

Please consider #35 (add FuzzEncodeFromJSON): none of the YAML libraries for Go pass this bar (I haven't checked libraries for other languages). It would be a good signal to the community if this project would show progress on that front. Or at least acknowledge the problem which I have reported one year ago.

[mrueg]

Question regarding the vanity URL, was/is it an option to take over the existing gopkg.in/yaml one from the original author?
If so, that would make migration to this fork much smoother.

[ingydotnet]

That's not something that was on the table.
It's also not the direction we chose to follow.

[scop]

For some reason I don't see a way to open a new discussion (there's no "New discussion" button anywhere that I can find, even though it is shown in various other projects), so (ab)using the possibility to reply here:

When doing my first migrations from the gopkg.in/yaml.vX packages to this one, I wanted to check the diffs from old to new. I posted them and the diff generator scripts as gists, and have linked to them in descriptions of migration PR's I've done here and there. Do feel free to link to these wherever anyone feels they might be useful:

• gopkg.in/yaml.v2@v2.4.0 to go.yaml.in/yaml/v2@v2.4.1: https://gist.github.com/scop/57f94f2bf97fb6a2d01349fa59d88530
• gopkg.in/yaml.v3@v3.0.1 to go.yaml.in/yaml/v3@v3.0.2: https://gist.github.com/scop/6ec72debf62a9603cff9dc97e6814ddd

[ingydotnet]

You don't see that green [New discussion] button?

[scop]

As said, no.

Also as noted, I do see it with various other repos, for example in https://github.com/jdx/mise/discussions

[andig]

Neither do I- no New Discussion button.

[ingydotnet]

I spent 20 minutes looking around. https://docs.github.com/en/discussions/quickstart#creating-a-new-discussion says:

Any authenticated user who can view the repository can create a discussion in that repository.

Can you try to reproduce this on some other repositories and figure out what's up?

stumped for now

[scop]

I clicked through quite a few projects that have discussions and could not reproduce anywhere else.