trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      slars/fix-pintura-config-path
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    🐛 Fixed Pintura config detection reading the wrong config path no ref The server emits pintura at the top level of the public config (public-config/config.js) and Ember Admin reads it there. usePinturaConfig looked under hostSettings.pintura, which nothing emits, so hosts configuring Pintura via server config fell back to the pintura_js_url/pintura_css_url settings. When those settings are unset the editor silently failed to open for the framework-hook consumers: the tag feature image, the member welcome-email editor, and the automations email editor.
    nx run ghost-monorepo:lint:boundaries
Succeeded
Linux
4 CPU cores
read-write access token used
c266c25f30145

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