Skip to content

chore(main): release altertable-lakehouse 0.6.0 - #32

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--altertable-lakehouse
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--altertable-lakehouse

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.6.0 (2026-11-02)

Features


This PR was generated with Release Please. See documentation.

@albert20260301

Copy link
Copy Markdown
Contributor

@leonkenneth The generated 0.6.0 release correctly makes the feature-level bump from 0.5.1 and contains only the manifest, package version, and changelog entry for #31. No CI checks are reported for this Release Please branch. Please review the release metadata before merge.

@albert20260301

Copy link
Copy Markdown
Contributor

@leonkenneth following up on the generated 0.6.0 release PR: it remains unreviewed and has no reported CI checks. Could you review the version, changelog, and release metadata before merge? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leonkenneth following up on the generated 0.6.0 release PR: it remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata before merge? I have not changed the generated branch.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable-lakehouse branch from ec11d75 to 4dd37c0 Compare November 2, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant