chore(release): 0.56.0 — maintenance re-release for reference-data delivery#389
Merged
Conversation
…ge projects Surfaced by running the E2E suite in CI against a GCP / Snowflake-keypair project (the new nightly e2e.yml from #385). All findings are test/environment robustness, NOT product bugs -- no product code changed. - ConfigSecretEncryption (x2): read `created["data"]["id"]`, not `created["id"]`. `config new --push` returns the standard `{status, data}` envelope; the test forgot to unwrap `["data"]` (the sibling `_test_config_new_push` already does). Manifested as `KeyError: 'id'`. - swap-tables rejection test: assert `"requires a branch"` instead of the old `"dev branch"` wording. The wording was corrected in #373 (swap works on any branch, incl. production); the CLI test was updated there but this E2E assertion was missed. - FullE2E workspace password: keypair-auth workspaces (Snowflake person-keypair login) have no password, so the API returns HTTP 400 "not supported for login type ..." -- skip that step cleanly instead of failing the whole run. - metastore_scope_available preflight: also treat an unreachable metastore host (connection error) as "scope unavailable" and skip, so a misconfigured stack URL yields one clean skip instead of a wall of errors across every dependent test.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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.
Why
0.55.0lived inmainacross three successive builds (#383 sync-secret audit → #379semantic-layer reference-data→ #388 its changelog) under one version number beforev0.55.0was tagged. Users who installed an interim 0.55.0 build do not receive thereference-datacommands viakbagent update: the auto-update check is version-only —Fix
Bump to 0.56.0 so
/releases/latestadvertises a strictly-greater target.Version("0.55.0") < Version("0.56.0")→ auto-update reinstalls → thereference-datasub-app (#379) and the rest of 0.55.0 reach every user.Scope
make version-syncpropagated plugin.json / marketplace.json / uv.lock).since v0.55.0doc tags remain correct.make checkgreen (3843 passed; lint/format/version/changelog/skill clean).