Skip to content

chore(main): release 0.2.0#8

Merged
gjtorikian merged 1 commit into
mainfrom
release-please--branches--main--components--emulate
Jul 12, 2026
Merged

chore(main): release 0.2.0#8
gjtorikian merged 1 commit into
mainfrom
release-please--branches--main--components--emulate

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.0 (2026-07-12)

Features

  • add response-shape conformance codegen and test (#9) (358773b)
  • provide an end-to-end login flow story with spec-accurate webhooks (#2) (fa39dfe)
  • seed M2M apps and API keys (#10) (f761419)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Jun 25, 2026

Copy link
Copy Markdown

Greptile Summary

This PR prepares the 0.2.0 release. The main changes are:

  • Package version updated to 0.2.0.
  • Lockfile root metadata updated to match.
  • Release Please manifest advanced to 0.2.0.
  • Changelog entry added for the 0.2.0 release.

Confidence Score: 5/5

The release metadata and changelog updates are consistent with the 0.2.0 release.

The changed files are limited to release metadata, lockfile metadata, and changelog content. The package version, lockfile root metadata, Release Please manifest, and changelog entry all align with the intended 0.2.0 release.

None.

T-Rex T-Rex Logs

What T-Rex did

  • Baseline state was captured, showing base values of 0.1.0 and no 0.2.0 changelog entries.
  • Post-change state was captured, showing head values of 0.2.0 and that all required changelog feature claims evaluate true.
  • The baseline and post-change logs were inspected to confirm the executed commands, working directories, structured assertion outputs, and exit codes are present.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (3): Last reviewed commit: "chore(main): release 0.2.0" | Re-trigger Greptile

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--emulate branch from fb4c054 to 05a654e Compare June 26, 2026 19:29
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--emulate branch from 05a654e to bfaff1b Compare July 12, 2026 19:27
@gjtorikian gjtorikian merged commit 58b0a08 into main Jul 12, 2026
5 checks passed
@gjtorikian gjtorikian deleted the release-please--branches--main--components--emulate branch July 12, 2026 19:28
@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

Development

Successfully merging this pull request may close these issues.

1 participant