go_1_20: 1.20.8 -> 1.20.9

[mfrw]

Description of changes

Changelog: https://go.dev/doc/devel/release#go1.20

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[fabianhjr]

Rebuilds seem low, could this go to the main branch directly?

[mfrw]

Rebuilds seem low, could this go to the main branch directly?

I can retarget this to master. I was not aware of how many rebuilds would happen at the time I made the PR so thought better to target staging.

Should I go ahead and retarget this ? @fabianhjr

[fabianhjr]

Sure, though note that you may need to rebase your branch to the merge-base before changing the target branch in github to avoid a mass ping. (More info at https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging )

[mfrw]

Sure, though note that you may need to rebase your branch to the merge-base before changing the target branch in github to avoid a mass ping. (More info at https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging )

Even though you gave such a nice pointer, I still managed to mess it up :(
Sincere apologies @fabianhjr

[fabianhjr]

Happens from time to time. 😅

Will diverge from the procedure merge when ofborg succeeds since notifications are low enuough and change is small enough.

[fabianhjr]

Oh no, I messed up to I apologize as well, lost track of where the default go version change was so far.

#254878

Could you create a new pull request targeting staging-next?

Reference

go, buildGoModule, buildGoPackage: default to 1.21

    [python-updates](https://github.com/NixOS/nixpkgs/compare/python-updates) ([#254878](https://github.com/NixOS/nixpkgs/pull/254878)) [staging](https://github.com/NixOS/nixpkgs/compare/staging) ([hllizi/nixpkgs#1](https://github.com/hllizi/nixpkgs/pull/1), [#254878](https://github.com/NixOS/nixpkgs/pull/254878)) [staging-next](https://github.com/NixOS/nixpkgs/compare/staging-next) ([#257792](https://github.com/NixOS/nixpkgs/pull/257792), [#254878](https://github.com/NixOS/nixpkgs/pull/254878))