chore(release): prep v1.11.0#183
Merged
Merged
Conversation
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
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 this change is needed
Cuts a new minor release
v1.11.0to ship the four PRs merged tomainsincev1.10.1:token_credentialauth method (new feature → minor bump)view/snapshot/materialized_lake_viewmaterializations were droppingworkspace_namedbt docs generateretry storm on[SCHEMA_NOT_FOUND]/[TABLE_OR_VIEW_NOT_FOUND]How
Release-prep only — no functional code change:
src/dbt/adapters/fabricspark/__version__.pyfrom1.10.1→1.11.0(minor bump justified by the newtoken_credentialauth method in feat: add token_credential auth method #177)## v1.11.0section toCHANGELOG.mdsummarizing the four PRs above (generated via thegenerate-changelogskill from.temp/VERSION_CHANGELOG_FULL.md)The existing
v1.10.1section is preserved unchanged below the new entry.Test
N/A — release metadata only. CI on this branch will exercise the full
lint/build/testmatrix against the released code paths to confirm the bump is green before tagging.Per
docs/RELEASE_CHECKLIST.md, the next steps after this merges:mainv1.11.0againstmain(triggersrelease.yml→ PyPI publish)dbt-fabricspark==1.11.0on pypi.org