chore: release 0.1.45

[akbarsaputrait]

Summary\n- Update changelog for 0.1.45\n\n## Notes\n- Branch contains changelog-only release commit.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
intent-example	Ignored	Preview	Sep 7, 2026 4:46pm UTC

[claude]

Review Summary

Scope: Changelog-only release PR — the diff adds a [0.1.45] section to CHANGELOG.md (15 additions, no deletions, 1 file). No source code, edge functions, auth/RLS, migrations, or payment/payout logic are touched.

Findings: None.

• No P0: no secrets/keys/JWTs, no auth or RLS changes, no edge-function deploy config, no mirror-table writes, no payment logic, no receiver-address changes.
• No P1 / P2: entries are well-formed, commit links/hashes are consistent, and the version + date (0.1.45 / 2026-09-06) follow the existing Keep a Changelog + SemVer format used in the file.

No blocking issues from this review. (Not approving/merging per instructions — verdict left to the automated step.)

🤖 Generated with Claude Code

[claude]

Pre-merge review — chore: release 0.1.45

Verdict: no blocking issues (0 P0).

This is a release-only PR. The diff is limited to four files and contains no code, payment/payout, auth, or RLS changes:

• CHANGELOG.md — adds the 0.1.45 section summarizing the Stellar deeplink / memo-guard work merged separately.
• packages/connectkit/package.json — 0.1.45-beta.4 → 0.1.45.
• examples/nextjs-app/package.json — dependency bump to 0.1.45.
• pnpm-lock.yaml — matching specifier + integrity-hash update.

Checks:

• ✅ Version bump is consistent across both package.json files and the lockfile.
• ✅ No secrets, keys, JWTs, or credentials introduced.
• ✅ No edge-function, Supabase RLS, or auth changes.
• ✅ No changes to payment/payout/withdrawal logic (the referenced feature/fix commits are not part of this diff, so they are out of scope for this review).

Note (non-blocking): the actual behavioral changes advertised in the changelog (Stellar deeplink generation, memo guard/warning text, deposit payload hardening) are not in this PR — they should have been reviewed/tested in their own PRs. If they haven't been, that review should happen there, not gated by this release bump.

No inline comments — nothing in the diff warrants one.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1a2e823706

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Bump the package manifest before declaring 0.1.45 stable

If a v0.1.45 tag is cut from this release commit, .github/workflows/release.yml lines 31-32 publishes @rozoai/intent-pay directly from packages/connectkit, whose manifest still reports 0.1.45-beta.4; therefore the workflow cannot publish the stable 0.1.45 announced here. The checked npm publish documentation confirms that publishing a folder uses its package.json and publishes that name/version combination, and the preceding 0.1.44 release updated the manifest, example dependency, and lockfile alongside the changelog. Include those version updates before labeling this as the stable release.

Useful? React with 👍 / 👎.

[tg-reviewer-shawnmuggle]

Automated code review — P0=0 P1=0 P2=0

Release metadata consistently promotes intent-pay from 0.1.45-beta.4 to 0.1.45 and updates the example dependency, lockfile, and changelog; no actionable defects found.

Reviewer: gpt-5.6-sol-low
Approved for this exact head SHA; the PR author decides when to merge.