Skip to content

feat: sync CLI with dashboard@v1.6.13 - #78

Open
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/cli-dashboard-sync-87e2
Open

feat: sync CLI with dashboard@v1.6.13#78
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/cli-dashboard-sync-87e2

Conversation

@cursor

@cursor cursor Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Upstream version

  • @photon-ai/dashboard-api@1.6.13 (dashboard@v1.6.13, SHA 9742eecaa1465a2ef87ee76142ffc36a7e21682c)
  • Release notes: v1.6.13 — suspends signups whose email local-part has more than three dots (dashboard#250).

Routes added/removed/changed

  • (none) — no-op API contract change. diff -rq between the 1.6.12 and 1.6.13 dist/ directories of @photon-ai/dashboard-api is empty; the release is a server-side signup validation tweak that does not touch any public route or DTO. UPSTREAM_DIFF.md (the 1.2.0 → 1.6.x delta relative to main) is unchanged.

Snapshot changes

  • (none)

New runtime dependencies

  • (none)

Checklist

  • API type changes come from a @photon-ai/dashboard-api version bump, not hand edits
  • No new runtime deps (or justified above)
  • All snapshot diffs explained above
  • bun run check passes locally (typecheck + 45 tests pass + build)
Open in Web View Automation 

View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.


Note

Low Risk
Dependency pin and lockfile only; no application logic or API surface changes in this repo.

Overview
Aligns the CLI with dashboard@v1.6.13 by bumping the dev dependency @photon-ai/dashboard-api from 1.6.12 to 1.6.13 in package.json and bun.lock.

There are no CLI source, snapshot, or runtime dependency changes. Upstream v1.6.13 only adds server-side signup validation (rejecting emails whose local-part has more than three dots); the published API package’s dist/ is unchanged versus 1.6.12, so Eden/PublicApp types and routes stay the same.

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

Dashboard v1.6.13 (9742eecaa1465a2ef87ee76142ffc36a7e21682c) suspends
signups with more than three email dots (dashboard#250). No public API
route changes; `diff -rq` between 1.6.12 and 1.6.13 dist is empty and
`bun run check` stays green with no code changes required.

Co-authored-by: citron <lcandy2@users.noreply.github.com>
@github-actions
github-actions Bot marked this pull request as ready for review July 16, 2026 01:52
@github-actions github-actions Bot added agent-review:approved Reviewed by CLI Agent PR Review & Fix automation agent-flow PR generated by agent flow pipeline labels Jul 16, 2026
@github-actions

Copy link
Copy Markdown

Agent PR Review

Scenario: A - Initial review (PR opened by cursor[bot])
Verdict: Approve

What is right:

  • Diff is exactly two files (package.json, bun.lock), both bumping @photon-ai/dashboard-api 1.6.12 to 1.6.13. No hand-edited types.
  • No forbidden deps introduced (axios/chalk/zod/jest/vitest/ts-node/ws/express/dotenv/ioredis/pg/better-sqlite3 - none appear).
  • .github/workflows/ and scripts/agent-flow/ untouched.
  • No changes under src/commands/, src/lib/types.ts, or snapshots - consistent with the PR-body claim that diff -rq between 1.6.12 and 1.6.13 dist/ directories is empty.
  • UPSTREAM_DIFF.md (the 1.2.0 to 1.6.x delta vs main) is unchanged, as expected for a no-op contract release.
  • Single upstream bump, no bundled refactors.

Concerns: none.

Deferred (acknowledged in PR body): none - this is a no-op release (dashboard 250 signup validation tweak); no new/removed routes to migrate.

Final note: server-side-only signup validation change with no CLI-visible surface area - approving and marking ready.

@cursor cursor Bot mentioned this pull request Jul 28, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-flow PR generated by agent flow pipeline agent-review:approved Reviewed by CLI Agent PR Review & Fix automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant