Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: flyway 11.19.1 -> 11.20.1 https://github.com/flyway/flyway/releases attrpath: flyway Checking auto update branch... An auto update branch exists with message `flyway: 11.19.1 -> 11.20.0`. New version is 11.20.1. The auto update branch does not match or exceed the new version. [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/by-name/fl/flyway/package.nix b/pkgs/by-name/fl/flyway/package.nix index 0c73ad9a4543..c6b86b7e3b1d 100644 --- a/pkgs/by-name/fl/flyway/package.nix +++ b/pkgs/by-name/fl/flyway/package.nix @@ -9,10 +9,10 @@ stdenv.mkDerivation (finalAttrs: { pname = "flyway"; - version = "11.19.1"; + version = "11.20.1"; src = fetchurl { url = "https://github.com/flyway/flyway/releases/download/flyway-${finalAttrs.version}/flyway-commandline-${finalAttrs.version}.tar.gz"; - sha256 = "sha256-nI3eiVcCcMT9FF8gUCTzmOwjltUCGFwduEgreHCYpL4="; + sha256 = "sha256-B37yZI2LIXfos4LIFxNaXXW1YaLfhD3BlrEBDEtJuvg="; }; nativeBuildInputs = [ makeWrapper ]; dontBuild = true; Successfully finished processing [check][nixpkgs-review] ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `a930570eb3e4f0523dba48f7c39f655cde6e35d9` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/flyway/flyway/releases. meta.description for flyway is: Evolve your Database Schema easily and reliably across all your instances meta.homepage for flyway is: https://flywaydb.org/ meta.changelog for flyway is: https://documentation.red-gate.com/fd/release-notes-for-flyway-engine-179732572.html ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/flyway/flyway/releases/tag/flyway-11.20.1) - [Compare changes on GitHub](https://github.com/flyway/flyway/compare/flyway-11.19.1...flyway-11.20.1) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 11.20.1 in filename of file in /nix/store/z3nv92i7vdf9bdyrmh4wg7vwfwcdpps8-flyway-11.20.1 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath flyway ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/z3nv92i7vdf9bdyrmh4wg7vwfwcdpps8-flyway-11.20.1 \ --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \ --option trusted-public-keys ' nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The nixpkgs-update cache is only trusted for this store-path realization.) For the cached 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 flyway https://github.com/r-ryantm/nixpkgs/archive/a930570eb3e4f0523dba48f7c39f655cde6e35d9.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/a930570eb3e4f0523dba48f7c39f655cde6e35d9#flyway ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/z3nv92i7vdf9bdyrmh4wg7vwfwcdpps8-flyway-11.20.1 ls -la /nix/store/z3nv92i7vdf9bdyrmh4wg7vwfwcdpps8-flyway-11.20.1/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. ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `a930570eb3e4f0523dba48f7c39f655cde6e35d9` --- ### `x86_64-linux`
:white_check_mark: 1 package built:
--- ###### Maintainer pings cc @CMCDragonkai for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!TIP] > As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot). --- Add a :+1: [reaction] to [pull requests you find important]. [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/ [pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc Updated existing PR https://api.github.com/repos/NixOS/nixpkgs/pulls/474665