Repository navigation
fix(deps): update Zoi and compatible Jido dependencies - #37
Merged
Merged
Conversation
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.
Use Zoi 0.18.11 and the released Jido 2.4.0 default-state fix. The lock also uses Action 2.4.0 and Signal 2.3.2. Related: agentjido/jido#398.
Remove all
override: trueoptions from Mix dependencies. The development/test AI dependency is pinned tof24ffdc701c48a2c6894c95e7cb550b25a68ce9efrom agentjido/jido_ai#376. That AI commit also uses Hex Jido~> 2.4, so the dependency sources now agree. The AI dependency remains development/test only. Other lock entries are unchanged.Validation on Elixir 1.20.4 / OTP 29:
mix deps.get, changed-manifest format,mix compile --warnings-as-errors,mix test --seed 0 --max-cases 4, andmix hex.buildpassed. Result: 176 passed.GitHub CI is running on
cbb121064a57d79ab82c90b9bf23e3938147f429. No package release was run.