Skip to content

chore(main): release 0.7.2 - #72

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

chore(main): release 0.7.2#72
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--emulate

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.7.2 (2026-08-18)

Bug Fixes

  • auth: gate the password grant on email verification (#69) (799ef19)
  • sso: redeem an SSO code for a user-management session (#70) (b0ae0e8)
  • users: populate and shape linked OAuth identities (#71) (71f1322)
  • users: populate connected accounts and serve the spec's verbs (#73) (20b4989)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Aug 17, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the project metadata for the 0.7.2 release.

  • Bumps the package and Release Please manifest versions from 0.7.1 to 0.7.2.
  • Adds the 0.7.2 release notes and comparison links to the changelog.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
package.json Bumps the npm package version to 0.7.2, consistent with the release manifest and changelog.
.release-please-manifest.json Advances the root package's tracked release version to 0.7.2.
CHANGELOG.md Adds the generated 0.7.2 release entry with four bug-fix references.

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

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--emulate branch 2 times, most recently from ee33a72 to 67e02b0 Compare August 17, 2026 22:05
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--emulate branch from 67e02b0 to 697e77c Compare August 18, 2026 14:10
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.

0 participants