Merge staging-next into staging

This commit is contained in:
nixpkgs-ci[bot]
2026-08-31 06:20:17 +00:00
committed by GitHub
118 changed files with 84 additions and 62 deletions

View File

@@ -45,6 +45,8 @@
- `databricks-cli` has been updated from `0.290.2` to `1.x.x`, the first major release. OAuth tokens for interactive logins (`auth_type = databricks-cli`) are now stored in the OS-native secure store by default (Secret Service on Linux) instead of `~/.databricks/token-cache.json`; cached tokens from older versions are not migrated, so run `databricks auth login` once per profile after upgrading. To keep the previous file-backed storage, set `DATABRICKS_AUTH_STORAGE=plaintext` or add `auth_storage = plaintext` under `[__settings__]` in `~/.databrickscfg`. Additionally, the `vector_search_endpoints` DABs resource renamed `min_qps` to `target_qps` (and the `vector-search-endpoints` command renamed `--min-qps` to `--target-qps`). See the [upstream changelog](https://github.com/databricks/cli/blob/main/CHANGELOG.md) for details.
- Gradle 7 has been removed because it is end-of-life. Please [upgrade to a newer version of Gradle](https://docs.gradle.org/current/userguide/upgrading_version_7.html).
- `hurl` has been updated to `8.x.x` which has some breaking changes. See [upstream changelog](https://github.com/Orange-OpenSource/hurl/releases/tag/8.0.0) for details.
- The existing `wasm32-wasi` target has become `wasm32-wasip1` and `pkgsCross.wasi32` has become `pkgsCross.wasm32-wasip1`, aligning with LLVM's nomenclature. Aliases are in place and old forms will continue to be parsed but there might be some breakage if you're relying on the exact form of these (e.g., in sysroot paths).

View File

@@ -40,7 +40,7 @@
stdenv.mkDerivation (finalAttrs: {
pname = "beekeeper-studio";
version = "6.0.4";
version = "6.0.5";
src =
let
@@ -54,9 +54,9 @@ stdenv.mkDerivation (finalAttrs: {
fetchurl {
url = "https://github.com/beekeeper-studio/beekeeper-studio/releases/download/v${finalAttrs.version}/${asset}";
hash = selectSystem {
x86_64-linux = "sha256-smRbK5CxvpB/8kq3WqjBnpI229ygHUTElOadDi8Njsk=";
aarch64-linux = "sha256-bL/oCoyIVbC0J1wXcHo5a/flzOGuNIZkIJPOHbv9EKQ=";
aarch64-darwin = "sha256-DClBYrXriZXnOkSTXygLZ3tSnr6hin5CRF+OjFNQ+jQ=";
x86_64-linux = "sha256-AlimxfT2aMPXJQKU7NxSmhqhQApIWp1K5qd3wFRvo/w=";
aarch64-linux = "sha256-W+Avv/yKefGk64Wvz3rF7ehYkD73EbsMXqeQi/tXjtw=";
aarch64-darwin = "sha256-+NFFtfX4CxlzjBA8iAgexGIOx+5thEJ4iZR9ngkTsjI=";
};
};

View File

@@ -10,13 +10,13 @@
stdenv.mkDerivation (finalAttrs: {
pname = "fuse-overlayfs";
version = "1.17";
version = "1.18";
src = fetchFromGitHub {
owner = "containers";
repo = "fuse-overlayfs";
rev = "v${finalAttrs.version}";
hash = "sha256-oXSqyxe5+hsuFXKajuviqh2nKIz8Kw6rjLnb6XTF6GI=";
hash = "sha256-Us7FKKJrZH5l+NRIEw2b3RTAGw08YfsIBauwH866P8E=";
};
nativeBuildInputs = [

View File

@@ -9,7 +9,7 @@ The basic steps to add a new core are:
1. Add a new core using `mkLibretroCore` function (use one of the existing
cores as an example)
2. Add your new core to [`default.nix`](./default.nix) file.
2. Add your new core to [`packages.nix`](./packages.nix).
3. Try to build your core with `nix-build -A libretro.<core>`.
## Using RetroArch with cores

View File

@@ -125,7 +125,7 @@ mkLibretroCore rec {
})}
src=$(nix-build --no-out-link -A "$UPDATE_NIX_ATTR_PATH.src")
core_file="pkgs/applications/emulators/libretro/cores/melondsds.nix"
core_file="pkgs/by-name/li/libretroPackages/cores/melondsds.nix"
# find lines in the format:
# fetch_dependency(name url rev)

Some files were not shown because too many files have changed in this diff Show More