Skip to content

chore: install jest and run the tests in CI - #1026

Merged
Maelstromeous merged 1 commit into
perf/api-queue-memory-onlyfrom
chore/jest
Sep 29, 2026
Merged

Maelstromeous merged 1 commit into
perf/api-queue-memory-onlyfrom
chore/jest

Conversation

@Maelstromeous

Copy link
Copy Markdown
Member

No manual steps or intervention required.

Stacked on #1025. Merge that first, and GitHub retargets this one to main.

What this does

Validation done

  • yarn test: 3 of 3 pass. yarn run lint:check and yarn run build are clean, and no spec reaches dist/.
  • The publisher test went red when ApiMQPublisher was switched back to a durable declaration.

🤖 Generated with Claude Code

Mirrors the api's setup (ps2alerts/api#736): jest with ts-jest, specs
alongside the source, and a Tests workflow on every PR. The first spec
pins the API queue declarations, including the options that must match
the api's own declaration of api-queue-production.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Maelstromeous
Maelstromeous marked this pull request as ready for review September 29, 2026 11:23
@Maelstromeous
Maelstromeous merged commit 0db5cde into perf/api-queue-memory-only Sep 29, 2026
5 checks passed
@Maelstromeous
Maelstromeous deleted the chore/jest branch September 29, 2026 11:24
Maelstromeous added a commit that referenced this pull request Sep 29, 2026
* perf: keep api-queue-production in memory, off the disk

api-queue-production was durable, lazy and fed persistent messages, so
RabbitMQ 3.10 wrote every message to disk even though the api drains it to
about zero. It is now non-durable, non-lazy and published transient. The
delay queues stay durable, lazy and persistent.

Must match the api's declaration of the same queue (ps2alerts/api), and the
existing queue has to be deleted and redeclared once before deploy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore: install jest and run the tests in CI (#1026)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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