Bump airbyte_cdk in source-declarative-manifest manually #37331
Merged
Conversation
This file contains 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
|
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 @natikgadzhi and the rest of your teammates on |
natikgadzhi
force-pushed
the
04-15-bump_airbyte_cdk_in_source-declarative-manifest_manually
branch
from
a563a78 to
8e56cc3
Compare
|
Fixed dockerImageTag version, pushing up for CI |
|
QA checks are failing but it's fine, we should ship. Or wait for another change to overwrite this. |
girarda
approved these changes
Apr 16, 2024
natikgadzhi
deleted the
04-15-bump_airbyte_cdk_in_source-declarative-manifest_manually
branch
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.
What
Publishing workflow failed for airbyte_cdk 0.81.6 in upgrading source-declarative-manifest, so this PR fixed this manually.
Failed run: