-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
airbyte-ci: upgrade to dagger 0.9.6 #34321
airbyte-ci: upgrade to dagger 0.9.6 #34321
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on Graphite |
4708c56
to
5064719
Compare
5064719
to
02e8d9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nit: in all the places that we refer to "we use dagger" in the docs, we link to the 0.6.4 docs - we should update this.
Otherwise LGTM, hoping this does the trick!
Note to future self: This is a good dagger version upgrade reference PR for when want to update the dagger runner infrastructure versions again (SEO words)! |
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.