beekeeper-studio 4.0.3 -> 4.1.13 https://repology.org/project/beekeeper-studio/versions
attrpath: beekeeper-studio
Checking auto update branch...
An auto update branch exists with message `beekeeper-studio: 4.0.3 -> 4.1.10`. New version is 4.1.13.
The auto update branch does not match or exceed the new version.
[version]
[version] updated version and sha256
[rustCrateVersion]
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion]
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/by-name/be/beekeeper-studio/package.nix b/pkgs/by-name/be/beekeeper-studio/package.nix
index 6d7353ab9b43..3b7bbebc8165 100644
--- a/pkgs/by-name/be/beekeeper-studio/package.nix
+++ b/pkgs/by-name/be/beekeeper-studio/package.nix
@@ -7,7 +7,7 @@
let
pname = "beekeeper-studio";
- version = "4.0.3";
+ version = "4.1.13";
plat = {
aarch64-linux = "-arm64";
@@ -16,7 +16,7 @@ let
hash = {
aarch64-linux = "sha256-PdRGZedNMZtGPI6Za2T94yKXvk6JoMoAot/kFKsBqQs=";
- x86_64-linux = "sha256-P2HlCb0dai4cJlKcT9LLQ+njViD+oHS3KI2YdR5jR44=";
+ x86_64-linux = "sha256-Yfpm6//hhYVKX3YipzmFj3NgEsL2h3eW+9yC0yYiDgk=";
}.${stdenv.hostPlatform.system};
src = fetchurl {
Successfully finished processing
cachix "/nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/beekeeper-studio/versions.
meta.description for beekeeper-studio is: Modern and easy to use SQL client for MySQL, Postgres, SQLite, SQL Server, and more. Linux, MacOS, and Windows
meta.homepage for beekeeper-studio is: https://www.beekeeperstudio.io
meta.changelog for beekeeper-studio is: https://github.com/beekeeper-studio/beekeeper-studio/releases/tag/v4.1.13
###### Updates performed
- Version update
###### To inspect upstream changes
- [Release on GitHub](https://github.com/beekeeper-studio/beekeeper-studio/releases/tag/v4.1.13)
- [Compare changes on GitHub](https://github.com/beekeeper-studio/beekeeper-studio/compare/v4.0.3...v4.1.13)
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 4.1.13 with grep in /nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13
- found 4.1.13 in filename of file in /nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13
---
Rebuild report (if merged into master) (click to expand)
```
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
beekeeper-studio
```
Instructions to test this update (click to expand)
---
Either **download from Cachix**:
```
nix-store -r /nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13 \
--option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
--option trusted-public-keys '
nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
```
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted.
Or, **build yourself**:
```
nix-build -A beekeeper-studio https://github.com/r-ryantm/nixpkgs/archive/6fb9f98a4baa4a718bc34c3e612398724148dab5.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/6fb9f98a4baa4a718bc34c3e612398724148dab5#beekeeper-studio
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13
ls -la /nix/store/xrv50v8xw2qkgkrvx6pni354j4wva7nk-beekeeper-studio-4.1.13/bin
```
---
### Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as _failed to build_ independent of the
change, simply because they are already broken on the target branch.
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
---
###### Maintainer pings
cc @milogert @Alexnortung for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
Updated existing PR
https://api.github.com/repos/NixOS/nixpkgs/pulls/280661