trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionFailed
      slars/newsletter-verification-token-guard
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Fixed 500 on newsletter verification with a non-newsletter token ref https://linear.app/ghost/issue/PLA-375 Newsletter and settings email verification links are issued by two separate MagicLink services that share one single-use token store, so a support address token decodes cleanly on the newsletter side. Its payload is `{key, value}` rather than `{id, property, value}`, which left the model edit with an undefined id and knex throwing "Undefined binding(s) detected" as a 500. Validating the token payload up front mirrors the key allowlist the settings service already applies in verifyKeyUpdate, and turns the crash into a 400.
    nx run ghost:test:ci:integration
Succeeded
Linux
4 CPU cores
read-write access token used
7f9c6cff30281
91%

Cache hits

21 of 23 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

22 groups of tasks optimized.

See resource usage for your runs

Add the resource usage add-on to record CPU and memory per task on your run's main agent and trace slow runs or out-of-memory failures to the task that caused them.

Add resource usage

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools