Skip to content

chore(main): release altertable 1.3.0 - #54

Merged
leonkenneth merged 1 commit into
mainfrom
release-please--branches--main--components--altertable
Sep 12, 2026
Merged

leonkenneth merged 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

1.3.0 (2026-09-04)

Features

  • client: add batch track, identify, and alias (#53) (2aff25b)

This PR was generated with Release Please. See documentation.

@albert20260301

Copy link
Copy Markdown
Contributor

@leonkenneth could you review this release PR?

I picked you because Ruby is your ownership area. The generated 1.3.0 release updates the changelog, version file, and lockfile; it has no reported CI checks. The main review focus is whether the release contents and version are intended before merge.

@albert20260301

Copy link
Copy Markdown
Contributor

@leonkenneth the 1.3.0 release PR is approved, but GitHub has continued to report an UNSTABLE merge state with no checks for four days.

Could you inspect the mergeability state and decide whether it is safe to merge? I have not changed the generated release branch.

@leonkenneth
leonkenneth merged commit d0889d0 into main Sep 12, 2026
6 checks passed
@leonkenneth
leonkenneth deleted the release-please--branches--main--components--altertable branch September 12, 2026 09:27
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

2 participants