OPENSPEC V1.4.1 RESTORES `OPENSPEC UPDATE` FOR WORKSPACE.YAML PROJECTS (E.G., DAGSTER)
OpenSpec v1.4.1 fixes the broken openspec update command for projects that maintain their own workspace.yaml, including Dagster setups. The [v1.4.1 release](ht...
OpenSpec v1.4.1 fixes the broken openspec update command for projects that maintain their own workspace.yaml, including Dagster setups.
The v1.4.1 release restores normal behavior for openspec update in repos that include a workspace.yaml, which had caused runs to fail or be skipped.
If you run OpenSpec in CI for Dagster or similar mono-repos, upgrade to v1.4.1 and re-test pipelines; you can drop any temporary workarounds.
Pipelines using workspace.yaml (like many Dagster repos) can run openspec update reliably again.
Removes manual patches and reduces drift from skipped or failing update steps.
-
terminal
In a repo with workspace.yaml, run openspec update before and after upgrading to v1.4.1; diff outputs and confirm CI exit codes pass.
-
terminal
In mono-repos, validate module discovery and path resolution during openspec update to catch any lingering edge cases.
Legacy codebase integration strategies...
- 01.
Pin OpenSpec to v1.4.1 in CI and remove any workarounds added for workspace.yaml repos.
- 02.
Rebuild and re-lock generated artifacts to ensure no unexpected diffs post-fix.
Fresh architecture paradigms...
- 01.
Safe to standardize an openspec update step in new pipelines that use workspace.yaml layouts.
- 02.
Adopt consistent CI guardrails (hash/diff checks) around spec generation from day one.
Get daily OPENSPEC + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday