ci: update .buildkite manifest, add Revise, Infiltrator #4187
+60
−35
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
haakon-e
changed the title
2 tasks
imreddyTeja
approved these changes
Dec 23, 2025
haakon-e
force-pushed
the
he/ci-add-revise-infiltrator-to
branch
from
b619de9 to
a9ddf4b
Compare
- fix Poppler_jll to v24
haakon-e
force-pushed
the
he/ci-add-revise-infiltrator-to
branch
from
a9ddf4b to
1ea1405
Compare
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.
This pull request updates the Julia project and its dependencies to newer versions and adds two development tools to the environment. The main changes are version bumps for several packages in
.buildkite/Manifest-v1.11.tomland the inclusion ofInfiltratorandRevisein.buildkite/Project.tomlfor enhanced debugging and live code reloading.The inclusion of these new packages is a practical one: Many of us use them while debugging. However, loading them in your base
(@v1.11)environment may lead to inconsistent versions between sub-dependencies. Adding them directly, ensures consistent versions and availability for all developers. Once the model is much more mature, it may be fine to remove these from the project environment again again.