You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
update-pyproject-dependencies and the downstream .github/workflows/pyproject-release.yml currently allow us to specify how semantically-versioned packages should be pinned en-masse (with a default to pin things as strictly as possible, i.e. patch-level). It would be nice to be able to override this on a per-package basis. My current thought is to introduce three new inputs: per-package-semantic-patch/minor/major-upper-bound, which are space separated lists of package names that default to an empty string.
Concretely, this will allow us to release the pyiron_snippets pin to only hold major versions, as discussed in today's team meeting.
The text was updated successfully, but these errors were encountered:
update-pyproject-dependencies
and the downstream.github/workflows/pyproject-release.yml
currently allow us to specify how semantically-versioned packages should be pinned en-masse (with a default to pin things as strictly as possible, i.e. patch-level). It would be nice to be able to override this on a per-package basis. My current thought is to introduce three new inputs:per-package-semantic-patch/minor/major-upper-bound
, which are space separated lists of package names that default to an empty string.Concretely, this will allow us to release the
pyiron_snippets
pin to only hold major versions, as discussed in today's team meeting.The text was updated successfully, but these errors were encountered: