Skip to content

chore(main): release altertable 0.3.0 - #14

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

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

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.3.0 (2026-11-09)

Features

  • add audience collection mode (#15) (9e507b8)
  • api: support native server batch overloads (#13) (eaaa8c4)
  • deprecate analytics environment routing (#16) (0bac9a6)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable branch from f5a2e14 to c1f5612 Compare September 7, 2026 07:19
@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable could you review this release PR?

I picked you because history on the generated release files has no core-team ownership signal and Python is your area. The generated 0.3.0 release PR has had no review or reported CI checks since September 7. The main review focus is whether the version, changelog, and release metadata are correct before merge. I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up on the generated 0.3.0 release PR: it remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata when you have capacity? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up: the generated 0.3.0 release PR remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata when you have capacity? I have not changed the generated branch.

3 similar comments
@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up: the generated 0.3.0 release PR remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata when you have capacity? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up: the generated 0.3.0 release PR remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata when you have capacity? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up: the generated 0.3.0 release PR remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata when you have capacity? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable the generated 0.3.0 release PR remains unreviewed with no reported CI checks. Could you review the version, changelog, and release metadata? I have not changed the generated branch.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up: the generated 0.3.0 release PR 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.

@albert20260301

Copy link
Copy Markdown
Contributor

@leo-altertable following up on the generated 0.3.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 branch from c1f5612 to 457b84f Compare November 9, 2026 14:44
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--altertable branch from 457b84f to 9a895e2 Compare November 9, 2026 14:48
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