Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yq-go: 3.4.1 -> 4.4.1 #109897

Merged
merged 1 commit into from Jan 19, 2021
Merged

yq-go: 3.4.1 -> 4.4.1 #109897

merged 1 commit into from Jan 19, 2021

Conversation

davegallant
Copy link
Member

@davegallant davegallant commented Jan 19, 2021

Motivation for this change
V4 is now officially released, it's quite different from V3 (sorry for the migration), however it is much more similar to jq, using a similar expression syntax and therefore support much more complex functionality!

If you've been using v3 and want/need to upgrade, checkout the upgrade guide.

Support for v3 will cease August 2021, until then, critical bug and security fixes will still get applied if required.

https://github.com/mikefarah/yq#v4-released

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@kalbasit kalbasit merged commit dd3238c into NixOS:master Jan 19, 2021
pjjw pushed a commit to pjjw/nixpkgs that referenced this pull request Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants