trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      chore/ber-3797-limit-custom-fields
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Added a host limit that can switch custom member fields off per site Custom member fields are intended for one Ghost(Pro) plan and above, but nothing could express that. A labs flag says a feature does not exist yet, which is the wrong thing to tell someone whose plan simply does not include it, and it is the same answer for every site. This adds limitCustomFields alongside the other flag limits the host already sets, so the decision about which plan carries the feature is configuration on the hosting side rather than a change to Ghost. It stays open unless a host switches it off, so nothing changes for anyone until that configuration exists. The routes that exist only to change field definitions sit behind one guard, and Admin asks the same question before offering any of it, so a publisher whose plan excludes the feature is told so rather than shown a door that refuses them.
    nx run-many -t test:unit -p @tryghost/admin-x-framework,@tryghost/activitypub,@tryghost/admin,ghost
Succeeded
Linux
4 CPU cores
read-write access token used
81b62b5030512
79%

Cache hits

26 of 33 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

30 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubGhostWorkspace