Run details

GhostWorkspace

CI Pipeline Executions
- Current executionSucceeded
  chore/limit-service-declared-names
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Made the set of limit names a declared one The manifest was already the allowlist the loader applies, but only at runtime: a caller could ask about any name at all, and asking about one nobody had declared quietly answered that the site was not limited. That is the same shape as a typo, and nothing told them apart. The names are now taken from the manifest itself, so asking about a limit that has not been declared does not compile. The loader narrows the host's spelling onto that set, which is the one place a name arrives as text and the only place it needs checking at runtime. Ghost's own route guard and Admin's limiter take the same set, and Admin names the limit a private feature depends on rather than describing it as a string.

nx run-many -t test:unit -p @tryghost/admin-x-framework,@tryghost/activitypub,@tryghost/admin,ghost,@tryghost/limit-service

Succeeded

4 CPU cores

read-write access token used

8c7b9fb130778

78%

Cache hits

28 of 36 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

32 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

GhostWorkspace