python312Packages.dash: 3.0.0 -> 3.0.2#393150
Conversation
|
There is already a PR open, we'll merge that first |
df41aad to
cc6625c
Compare
|
IIRC stringcase can be removed from deps |
6a01370 to
83b096f
Compare
83b096f to
8fad466
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript. meta.description for python312Packages.dash is: Python framework for building analytical web applications meta.homepage for python312Packages.dash is: https://dash.plot.ly/ meta.changelog for python312Packages.dash is: https://github.com/plotly/dash/blob/v3.0.2/CHANGELOG.md Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from the cache: (The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
8fad466 to
3bd056c
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.dash is: Python framework for building analytical web applications
meta.homepage for python312Packages.dash is: https://dash.plot.ly/
meta.changelog for python312Packages.dash is: https://github.com/plotly/dash/blob/v3.0.1/CHANGELOG.md
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(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-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
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-reviewresultGenerated using
nixpkgs-review.Command:
nixpkgs-reviewx86_64-linux❌ 2 packages failed to build:
✅ 18 packages built:
Maintainer pings
cc @antoinerg @TomaSajt for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.