Since rust-analyzer's publisher on the VSCode marketplace was changed to
rust-lang, this makes the extension available under
vscode-extensions.rust-lang.rust-analyzer. I thought I already did this
in PR #173540, but apparently I forgot. This is backwards-compatible in
that the extension is still availabe at
vscode-extensions.matklad.rust-analyzer as well.
* Add post-build script to generate autoloads file.
* Bump upstream revision to get a critical bugfix that prevented this library's
main function from executing.
The source for setting the path is slightly different, so relax the
search/replace term, so it works with the new version.
Fixes starting the web-preview process.
* origin/staging-next: (62 commits)
Re-Revert "lua: fix on darwin by using makeBinaryWrapper (#172749)"
openldap: fix cross-compilation
makeBinaryWrapper: fix codesign on aarch64-darwin
python3Packages.ldap: fix linking with openldap 2.5+
Revert "lua: fix on darwin by using makeBinaryWrapper (#172749)"
wine: enable parallel build again
pkgsi686Linux.gdb: fix formatting for 32-bit systems
gtk4: Fix incorrect merge
nixos/openldap: use upstream unit defaults
openldap: update maintainers
openldap: 2.4.58 -> 2.6.2
Revert "Add mingwW64-llvm cross-system."
lua: fix on darwin by using makeBinaryWrapper (#172749)
python310Packages.python-mimeparse: execute tests
pandas: fix darwin build
gtk3: 3.24.33 -> 3.24.33-2022-03-11
gtk4: patch fixing g-c-c crashes
e2fsprogs: patch for CVE-2022-1304
firefox-unwrapped: fix cross compilation
rustc: expose correct llvmPackages for cross compile
...
This update changes the extension's publisher from "matklad" to
"rust-lang" and moves it to `vscode-extensions.rust-lang.rust-analyzer`,
but keeps `vscode-extensions.matklad.rust-analyzer` for backwards
compatibility. It also bumps the version number from 0.2.xxx to 0.3.xxx,
as described in changelog #129.5:
https://rust-analyzer.github.io/thisweek/2022/05/17/changelog-129-5.html
The release tag was out-of-date even though the extension was updated
regularly. Ideally, the update script might increment it on its own,
like the rust-analyzer update script already does.
