-
Notifications
You must be signed in to change notification settings - Fork 1
Bump pyiron-workflow from 0.13.3 to 0.14.0 #586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@dependabot rebase |
a85b0d0 to
37dfcde
Compare
|
@dependabot recreate |
1450e1a to
426f177
Compare
@liamhuber I am confused by the mpi4py on bagofholding - I did not see this in the bagofholding package?! |
It's in the requirements and env file at least since v0.1.0, so it is correct that it appears in the feedstock. You're correct that it does not explicitly appear in the tests. I added it here in this commit because otherwise I couldn't get Otherwise, |
No, the dependencies on HEAD are already the latest versions of both Reading the error log more carefully, I see it's actually our lower bound of |
Just down to the last major version to see if that will help pyiron/docker-stacks#586 Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
|
@niklassiemer, it looks safe to just drop it: pyiron/bagofholding#75. I've merged that and removed the dependency from HEAD. We could release a new |
|
@dependabot recreate |
5546adc to
2796de5
Compare
|
https://github.com/dependabot recreate |
fec5692 to
bce244d
Compare
|
A newer version of pyiron-workflow exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
|
@dependabot recreate |
Bumps [pyiron-workflow](https://github.com/pyiron/pyiron_workflow) from 0.13.3 to 0.14.0. - [Release notes](https://github.com/pyiron/pyiron_workflow/releases) - [Commits](pyiron/pyiron_workflow@pyiron_workflow-0.13.3...pyiron_workflow-0.14.0) --- updated-dependencies: - dependency-name: pyiron-workflow dependency-version: 0.14.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
e37df82 to
178aa64
Compare
|
Superseded by #605. |
Bumps pyiron-workflow from 0.13.3 to 0.14.0.
Release notes
Sourced from pyiron-workflow's releases.
Commits
9592209Only run the slurm jobs on PRs (#725)b039a3cSafer input update (#724)175ac09Better rerun (#723)ce220ddDisallow loading into running nodes (#721)3fa161fPurge old serialization approach (#720)648a057Update readme (#719)d9e710bExtend APIs with executor stuff (#718)7ccdabdAdd a flag to rerun (#717)e0e1510Let threadpools be (#716)309c68fNo running cache hit (#714)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)