3 people caa0db4692 docs(server): explain why the seed's issue idempotency key is not revision-scoped ...

Cloud's reconcile runs off portfolio fetches, which can overlap, so two
pushes of the same revision can race. The idempotency key on the first
task is what makes that safe. It is deliberately company-scoped rather
than revision-scoped, so that a later revision still dedupes against
whatever the first push created if the recorded issue id is lost. That
reasoning was not obvious from the call site.

Co-authored-by: Paperclip <noreply@paperclip.ing>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-13 18:21:44 -07:00

..

scripts

fix(server): use stable tsx/cli entry point in dev-watch

2026-03-28 06:42:03 +07:00

src

docs(server): explain why the seed's issue idempotency key is not revision-scoped

2026-08-13 18:21:44 -07:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

fix(server): export manual OpenTelemetry spans (#10565)

2026-07-31 12:47:57 -07:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

vitest.config.ts

fix(test): stop flaky server-suite afterAll hook timeouts (#10024)

2026-07-22 11:51:30 -07:00