Dashboard › craft › Craft workspace resolver reaches releas…
019f899e-90e8-7764-9cc8-d32226ca34d2| Project | Hits | Last recalled |
|---|---|---|
| cli | 1 | 8d ago |
In getsentry/craft's workspaces redesign, config.releaseBranchPrefix (used to build branch names as ${prefix}/${version} in both prepare.ts and publish.ts) is already resolved per-workspace via the PR B resolver, since it comes from getConfiguration(). Same for version resolution, changelog config, tag prefix, and github config (via getGlobalGitHubConfig()) — all workspace-aware helpers. When extending workspace support to a new command/pipeline, first check whether the value already flows through getConfiguration()/workspace-aware helpers before assuming new threading code is needed — most of the pipeline requires none. The one gap found (as of PR C) was publishState.ts, which builds its own filename key independently of config resolution — see [[gotcha-publishstate]].