release: v0.21.2 — customer bugfix batch - #214
Merged
Merged
Conversation
.env.example and .env.template are documentation/scaffolding artifacts (e.g. for onboarding contributors) and should stay tracked even though the catch-all .env.* pattern would otherwise ignore them.
…, whitespace strip (#199) * fix(0.21.2): job run banner reads resolved id, hint threads branch_id, whitespace strip - Rich-mode "Bound variable values row" banner now reads resolvedVariableValuesId from the service response instead of echoing the raw --variable-values-id flag; shows the auto-resolved row even when the flag was omitted. - --variable-values-id input is stripped of surrounding whitespace before the empty-string guard; prevents a padded value from passing the guard and reaching the service unstripped. - --hint client job run --branch ID now threads branch_id through all three client calls (get_config_detail, list_config_rows, create_job); previously the branch arg was silently dropped, causing the rendered hint to target production even when a dev branch was specified. - rich.markup.escape import hoisted to module level in commands/job.py. - New tests: rich-mode resolved-id banner, whitespace strip forwarding, --no-variables JSON output excludes resolvedVariableValuesId, wait=True preserves resolvedVariableValuesId on the waited result, hint branch_id threading contract. * review: drop redundant str() in banner, remove PR reference from test docstring * chore: drop out-of-scope .gitignore whitelist (move to separate PR)
`kbagent config search` now pulls configurations with `include=configuration,rows` and feeds the full tree (including each row's `configuration` block) through the match function. Previously, rows were fetched only by `sync pull`, so searches for row-level properties (writer incremental flags, DB extractor credentials, etc.) always returned 0 matches, even though the help text promised coverage of row definitions. Fixes #196
Previously, `lineage build` relied on iterating subdirectories to find `<subdir>/.keboola/manifest.json`, which works for `sync pull --all-projects` (nested layout) but silently returned an empty graph for `sync pull --project X` (flat layout, manifest in CWD). Detects whether the target directory is itself a project (flat layout) and falls back to the existing multi-project iteration otherwise. Emits a warning when no projects are found with a hint about the expected layouts. Fixes #208
Storage read operations (tables, buckets, bucket-detail, table-detail, files) no longer follow the project's active dev branch automatically. The Storage API branch-scoped endpoint returns only tables/buckets that were locally modified in the dev branch, which for a freshly created branch is an empty set. Users with a dev branch active would therefore see "No tables found" until they reset the branch, defeating the purpose of dev branch isolation. Write and destructive storage ops stay branch-aware -- modifying a dev branch is the expected intent when the user is on one. Explicit `--branch <id>` continues to override in all cases. Fixes #207
…ands (#212) `storage tables` now accepts zero or more `--project` flags and queries all connected projects in parallel (same pattern as `storage buckets`, `config list`, `config search`, `job list`, `component list`). Previously it required exactly one `--project`, forcing users to shell-loop across projects for fleet-wide audits -- despite the SKILL documentation advertising "multi-project by default" for read commands. Parallel execution via BaseService._run_parallel; per-project errors accumulate into the response envelope (partial success does not abort others). Fixes #198
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.
Summary
Integration PR for v0.21.2 hotfix release, bundling 6 merged PRs into a single reviewable unit. All 6 PRs were squash-merged into
release/0.21.2in the order listed below; a single conflict between #211 and #212 incommands/storage.py+commands/context.pywas resolved during rebase (composition of both changes: `storage tables` is now multi-project and ignores the implicit active dev branch on single-project reads).Contents
Customer-reported bugs included
Conflict resolution notes
Rebase of #212 on top of #211 required resolving:
Pending before merge
Test plan
Post-merge