Skip to content

Conversation

@braydonk
Copy link
Collaborator

The yaml.v3 package upstream is now archived. This means there is no hope of my patches ever being committed upstream. As such, there is nothing to gain by maintaining this library in a separate repo. It will be easier for people to contribute to if it's in this repo.

I will keep github.com/braydonk/yaml alive purely for the select few who pull the package for the couple of patches that upstream never merged.

@braydonk braydonk force-pushed the yaml-coming-home branch from bb8ceae to f729f94 Compare May 17, 2025 12:19
The yaml.v3 package upstream is now archived. This means there is no hope of my patches ever being committed upstream. As such, there is
nothing to gain by maintaining this library in a separate repo.
It will be easier for people to contribute to if it's in this repo.
I will keep github.com/braydonk/yaml alive purely for the select few who pull
the package for the couple of patches that upstream never merged.
@braydonk braydonk force-pushed the yaml-coming-home branch from f729f94 to 5e9c2b2 Compare May 17, 2025 12:24
@ccoVeille
Copy link

Are you aware of this initiative?

https://github.com/yaml/go-yaml

@braydonk
Copy link
Collaborator Author

Are you aware of this initiative?

Nope, this is the first I'm hearing of it. Thanks for bring it to my attention. I'm gonna go forward with this anyway but I will see whether I can collaborate with them.

@braydonk braydonk merged commit 9e812c9 into main May 18, 2025
8 checks passed
steeef pushed a commit to steeef/yamlfmt that referenced this pull request Sep 5, 2025
* Vendor github.com/braydonk/yaml

The yaml.v3 package upstream is now archived. This means there is no hope of my patches ever being committed upstream. As such, there is
nothing to gain by maintaining this library in a separate repo.
It will be easier for people to contribute to if it's in this repo.
I will keep github.com/braydonk/yaml alive purely for the select few who pull
the package for the couple of patches that upstream never merged.

* fix test workflows cause the yaml package fails everything
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants