Bump analysis3 ilamb to 2.7.3#426
Closed
charles-turner-bot wants to merge 1 commit into
Closed
Conversation
Collaborator
|
Bot is useless here it seems, doing it myself. |
Collaborator
|
Thanks @charles-turner-1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #424.
This updates the analysis3 ILAMB pin from 2.7.2 to 2.7.3 across the pixi manifest and generated environment artifacts:
pixi.tomlenvironment.unlocked.ymlenvironment.ymlpixi.locksolved.jsonI couldn't get
pixito complete a local rebuild on this machine becausepixi 0.71.2is currently panicking in build-dispatch linking while solving the PyPI side of the environment. The ILAMB 2.7.3 conda metadata on conda-forge matches 2.7.2's dependency set, so the generated files here were updated consistently to the 2.7.3 artifact and CI can do the real end-to-end check.