edgedb: 4.1.1 -> 5.1.0

[0x50F1A]

Description of changes

• Update source from 4.1.1 to 5.1.0
• Re-vendor Cargo.lock
• Fix ELF patch
• Format with nixfmt

Diff: edgedb/edgedb-cli@v4.1.1...v5.1.0

Changelog: https://docs.edgedb.com/changelog/5_x

Things done

nix shell .#edgedb
edgedb -V
edgedb project init
# ...
edgedb
select "foo";
# {'foo'}
\quit
edgedb instance destroy -I nixpkgs --force
edgedb branch
rm -rf dbschema
rm edgedb.toml

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 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.

---

Add a 👍 reaction to pull requests you find important.

[kirillrdy]

while release notes don't include words such as "breaking changes"

there is

The CLI will first check to see if your schema will migrate cleanly to EdgeDB 5.0. If the upgrade check finds any problems, it will report them back to you.

currently all branches are in

Restrict all breaking changes with the exception of desktop environments

I would recommend to wait until 24.05 is released

[ahirner]

Format with nixfmt

Thx!
Builds and works for x86_64-darwin.

currently all branches are in

I observed that 5.1.0 does provide hints in a sane way, e.g. before changing dbschema/migration formats:

Anyway, I support to not backport and add a release note for 24.05.

This would still go to unstable, or is there another staging mechanism @kirillrdy ? Pardon if that should be obvious from Contributing.md.

[kirillrdy]

as per #303285

2024-05-01 all branches Restrict all breaking changes with the exception of desktop environments

you can set PR to draft and wait until Branch-off then it can be merged into master and will be part of 24.11 release

this all, assuming 5.x is considered "breaking changes" release, that I don't have a strong opinion about

[ahirner]

Breaking changes (FWIW) got unrestricted as of 2014-05-15.

[kirillrdy]

Breaking changes (FWIW) got unrestricted as of 2014-05-15.

Only for staging branch