WealthLedger/specs
5
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Убрать закрепление версии OpenSpec CLI (.cli-version, check-openspec) #67

New Issue
Closed
opened 2026-10-30 08:56:46 +03:00 by codex-bot · 1 comment
codex-bot commented 2026-10-30 08:56:46 +03:00
Owner
Copy Link
Copy Source

Контекст и результат

openspec/.cli-version (1.13.1) требует ручной синхронизации с глобально установленным CLI и уже расходится с ним (1.15.0). Решение владельца: не закреплять версию.

Acceptance Criteria

  • Удалены openspec/.cli-version, scripts/check-openspec.cjs и npm script check:openspec.
  • README не ссылается на них.
  • npm run verify проходит.
## Контекст и результат `openspec/.cli-version` (1.13.1) требует ручной синхронизации с глобально установленным CLI и уже расходится с ним (1.15.0). Решение владельца: не закреплять версию. ## Acceptance Criteria - [x] Удалены `openspec/.cli-version`, `scripts/check-openspec.cjs` и npm script `check:openspec`. - [x] README не ссылается на них. - [x] `npm run verify` проходит.
codex-bot commented 2026-11-03 06:53:00 +03:00
Author
Owner
Copy Link
Copy Source

Done in PR #78 (squash, develop 8b2b742). CI (3 runs) green before merge.

Change

  • Removed openspec/.cli-version, scripts/check-openspec.cjs, npm script check:openspec and its call in validate.
  • CI verify: npm install -g @fission-ai/openspec (latest) instead of the version from the file.
  • README describes no pin and why --strict is gone. Archived records in openspec/changes/archive/** mention 1.13.1 as past evidence and were left untouched (read-only).
  • Owner decision: --strict removed from validate as well. Since CLI 1.15 the warning "Requirement text is very long (>500 characters)" counts as an error in strict mode: 77 warnings in 19 canonical specs; openspec validate --all --strict on 1.16.0 gives 9 passed / 19 failed (on 1.13.1 it was INFO).

Evidence

  • npm run validate on global 1.15.0: 28 passed / 0 failed, lychee 0 errors. npm run verify and git diff --check: OK.
  • openspec validate --all --no-interactive alone on 1.13.1 and on 1.16.0 (latest): 28 passed / 0 failed on both.

Limits

  • Warnings stay in the output but no longer fail the check; returning to --strict first needs the 19 specs' long requirements split (separate Issue, not done here).
  • Node version is no longer verified by a script; CI takes it from .nvmrc via setup-node, locally engines in package.json applies.
  • Behaviour of future CLI versions not verified.
Done in PR #78 (squash, develop `8b2b742`). CI (3 runs) green before merge. ## Change - Removed `openspec/.cli-version`, `scripts/check-openspec.cjs`, npm script `check:openspec` and its call in `validate`. - CI `verify`: `npm install -g @fission-ai/openspec` (latest) instead of the version from the file. - README describes no pin and why `--strict` is gone. Archived records in `openspec/changes/archive/**` mention 1.13.1 as past evidence and were left untouched (read-only). - Owner decision: `--strict` removed from `validate` as well. Since CLI 1.15 the warning "Requirement text is very long (>500 characters)" counts as an error in strict mode: 77 warnings in 19 canonical specs; `openspec validate --all --strict` on 1.16.0 gives 9 passed / 19 failed (on 1.13.1 it was INFO). ## Evidence - `npm run validate` on global 1.15.0: 28 passed / 0 failed, lychee 0 errors. `npm run verify` and `git diff --check`: OK. - `openspec validate --all --no-interactive` alone on 1.13.1 and on 1.16.0 (latest): 28 passed / 0 failed on both. ## Limits - Warnings stay in the output but no longer fail the check; returning to `--strict` first needs the 19 specs' long requirements split (separate Issue, not done here). - Node version is no longer verified by a script; CI takes it from `.nvmrc` via `setup-node`, locally `engines` in `package.json` applies. - Behaviour of future CLI versions not verified.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Dependencies
Dependency update or dependency-management work
 Kind/Investigation
Research or decision required before implementation
 Kind/Process
Developer workflow, CI/CD, tooling, or process improvement
 Kind/Refactor
Internal code or configuration restructuring without new product behavior
 audit/2026-10-11
Technical Audit Remediation — 2026-10-11
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
codex-bot hermes-agent ksv741 publisher-bot renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: WealthLedger/specs#67