AJDA-2973 bump keboola-component to 1.11.0#29
Merged
Conversation
Pulls in the fix that scopes the manifest schema/legacy exclusivity guard to output manifests, so input tables carrying both the native `schema` node and legacy `columns`/`metadata`/`column_metadata` keys are accepted.
matyas-jirat-keboola
approved these changes
Jul 2, 2026
matyas-jirat-keboola
left a comment
matyas-jirat-keboola
left a comment
Contributor
There was a problem hiding this comment.
Reviewed: bump-only diff (keboola-component -> 1.11.0), CI green. AJDA-2973.
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
2 participants
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.
Link to issue
https://linear.app/keboola/issue/AJDA-2973/python-component-scope-manifest-schemalegacy-exclusivity-guard-to
Description
Bumps the
keboola-componentdependency from1.10.0to1.11.0(pyproject.tomlspecifier>=1.6.10→>=1.11.0, lockfile regenerated).1.11.0 ships the fix for AJDA-2973: the manifest
schema/legacy exclusivity guard is now scoped to output manifests only. Input table manifests that carry both the nativeschemanode and the legacycolumns/metadata/column_metadatakeys (the platform's deliberate backward-compatible contract after AJDA-2714) are now accepted instead of raisingUserException. This unblocks Python components reading typed input tables.Justification
See the linked issue. Without this bump, custom Python code reading typed input tables fails at manifest parse time.
Plans for Customer Communication
None — bug fix restoring expected behavior.
Impact Analysis
Dependency-only change. Picks up the library fix; existing precedence (
schemapreferred over legacy keys) is unchanged for already-working manifests. No feature flag. Affects all configurations of this component once the new image is deployed.Deployment Plan
Standard CI/CD — image is published from the merge commit, ArgoCD picks it up.
Rollback Plan
Revert this PR, or roll back to the previous image tag in ArgoGitops.
Post-Release Support Plan
None.