Skip to content

fix(api): correct pilot registration timeline - #76

Merged
BeforeLights merged 1 commit into
mainfrom
codex/platform-admin-seed-dates
Aug 21, 2026
Merged

BeforeLights merged 1 commit into
mainfrom
codex/platform-admin-seed-dates

Conversation

@BeforeLights

Copy link
Copy Markdown
Contributor

Summary

  • constrain the 63 synthetic customer registrations to June-August 2026
  • model 8 June, 39 July, and 16 August registrations
  • keep exactly four seeded customer registrations after August 14

Verification

  • node --test services/api/test/seed-local.test.mjs
  • corepack pnpm --filter @databreeze/api typecheck
  • corepack pnpm exec eslint services/api/scripts/seed-local.mjs services/api/test/seed-local.test.mjs
  • corepack pnpm exec prettier --check services/api/scripts/seed-local.mjs services/api/test/seed-local.test.mjs
  • git diff --check

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@BeforeLights, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c2372b2-14af-40aa-b944-a0c6c4f44826

📥 Commits

Reviewing files that changed from the base of the PR and between 98bb2aa and c18df57.

📒 Files selected for processing (2)
  • services/api/scripts/seed-local.mjs
  • services/api/test/seed-local.test.mjs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Aug 21, 2026

Copy link
Copy Markdown

Greptile Summary

Updates local platform-analytics seed data to model the requested June–August 2026 pilot registration timeline.

  • Distributes 63 synthetic registrations as 8 in June, 39 in July, and 16 in August.
  • Leaves exactly four registrations after August 14.
  • Adds a requirement-linked test covering monthly counts, the lower date boundary, and the post-August-14 count.

Confidence Score: 5/5

The PR appears safe to merge with no concrete blocking or non-blocking defects identified.

The generated dates produce the requested 8/39/16 monthly distribution and exactly four registrations after August 14, while the accompanying test directly covers those requirements.

Important Files Changed

Filename Overview
services/api/scripts/seed-local.mjs Adds deterministic UTC registration dates for synthetic users and keeps update timestamps chronologically after creation.
services/api/test/seed-local.test.mjs Verifies the requested monthly registration distribution and pilot-window boundaries.

Reviews (1): Last reviewed commit: "fix(api): correct pilot registration tim..." | Re-trigger Greptile

@BeforeLights
BeforeLights merged commit 24fce9b into main Aug 21, 2026
11 checks passed
@BeforeLights
BeforeLights deleted the codex/platform-admin-seed-dates branch August 21, 2026 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant