Skip to content

chore(v7): release ldai 0.10.0 - #424

Open
github-actions[bot] wants to merge 1 commit into
v7from
release-please--branches--v7--components--ldai
Open

chore(v7): release ldai 0.10.0#424
github-actions[bot] wants to merge 1 commit into
v7from
release-please--branches--v7--components--ldai

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.10.0 (2026-09-04)

Features

  • ldai: stamp modelKey and modelVersion on AI usage events (AIC-2850) (#414) (bd4ce7a)

This PR was generated with Release Please. See documentation.


Note

Overview
Release Please cut for ldai 0.10.0, updating the manifest entry, the Version constant in package_info.go, and the changelog for the new tag.

The 0.10.0 release notes document the already-merged feature that stamps modelKey and modelVersion on AI usage events (AIC-2850, #414). This PR does not change application logic—only version and release metadata.

Reviewed by Cursor Bugbot for commit 268dee8. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
github-actions Bot requested a review from a team as a code owner July 22, 2026 22:47
@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch 4 times, most recently from bc1b78d to ca045c9 Compare July 28, 2026 19:38
@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch 3 times, most recently from d6c3a85 to e44acac Compare August 18, 2026 15:41
@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch 5 times, most recently from dd80bbe to 91d280f Compare August 28, 2026 21:30
@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch from 91d280f to 94dc519 Compare September 2, 2026 17:13
@jsonbailey

Copy link
Copy Markdown
Contributor

This module and the work linked in this PR was performed on the new repo. It should not be merged.

@jsonbailey jsonbailey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The work was done in the new repo. Rejecting the PR to block it until we decide what to do with the module so new releases don't keep appearing.

@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch 4 times, most recently from 561059e to ea8e2f3 Compare September 3, 2026 21:02
@github-actions
github-actions Bot force-pushed the release-please--branches--v7--components--ldai branch from ea8e2f3 to 268dee8 Compare September 4, 2026 15:53
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