airbyte-ci: upgrade to dagger 0.9.6 #34321
Merged
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.
What
Closes #34110
Closes #34041
We want to use the latest dagger version in our pipelines and other internal packages using dagger
How
pyproject.toml
ofpipelines
,cat
,base_images
+ regenerate lock files0.9.6
to supported version in the infra inpipelines
Manual testing
airbyte-ci connector test
airbyte-ci connector publish
airbyte-ci test
airbyte-ci format
User impact
You can note that no workflow file change is required to propagate this upgrade. New runners are dynamically targetted thanks to the new
get_ci_runner
job, infering the runner from the airbyte-ci command.So no "please update your branch" is required 😄 :
--ci-requirements
on the jobs using the latest binary will output that 0.9.6 runners have to be used.