@fission-ai/openspec 0.19.0 → 0.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -11,7 +11,7 @@ const proposalSteps = `**Steps**
11
11
  4. Capture architectural reasoning in \`design.md\` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
12
12
  5. Draft spec deltas in \`changes/<id>/specs/<capability>/spec.md\` (one folder per capability) using \`## ADDED|MODIFIED|REMOVED Requirements\` with at least one \`#### Scenario:\` per requirement and cross-reference related capabilities when relevant.
13
13
  6. Draft \`tasks.md\` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
14
- 7. Validate with \`openspec validate <id> --strict\` and resolve every issue before sharing the proposal.`;
14
+ 7. Validate with \`openspec validate <id> --strict --no-interactive\` and resolve every issue before sharing the proposal.`;
15
15
  const proposalReferences = `**Reference**
16
16
  - Use \`openspec show <id> --json --deltas-only\` or \`openspec show <spec> --type spec\` to inspect details when validation fails.
17
17
  - Search existing requirements with \`rg -n "Requirement:|Scenario:" openspec/specs\` before writing new ones.
@@ -34,7 +34,7 @@ const archiveSteps = `**Steps**
34
34
  2. Validate the change ID by running \`openspec list\` (or \`openspec show <id>\`) and stop if the change is missing, already archived, or otherwise not ready to archive.
35
35
  3. Run \`openspec archive <id> --yes\` so the CLI moves the change and applies spec updates without prompts (use \`--skip-specs\` only for tooling-only work).
36
36
  4. Review the command output to confirm the target specs were updated and the change landed in \`changes/archive/\`.
37
- 5. Validate with \`openspec validate --strict\` and inspect with \`openspec show <id>\` if anything looks off.`;
37
+ 5. Validate with \`openspec validate --strict --no-interactive\` and inspect with \`openspec show <id>\` if anything looks off.`;
38
38
  const archiveReferences = `**Reference**
39
39
  - Use \`openspec list\` to confirm change IDs before archiving.
40
40
  - Inspect refreshed specs with \`openspec list --specs\` and address any validation issues before handing off.`;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fission-ai/openspec",
3
- "version": "0.19.0",
3
+ "version": "0.21.0",
4
4
  "description": "AI-native system for spec-driven development",
5
5
  "keywords": [
6
6
  "openspec",
@@ -42,6 +42,7 @@
42
42
  "node": ">=20.19.0"
43
43
  },
44
44
  "devDependencies": {
45
+ "@changesets/changelog-github": "^0.5.2",
45
46
  "@changesets/cli": "^2.27.7",
46
47
  "@types/node": "^24.2.0",
47
48
  "@vitest/ui": "^3.2.4",
@@ -75,7 +76,6 @@
75
76
  "check:pack-version": "node scripts/pack-version-check.mjs",
76
77
  "release": "pnpm run release:ci",
77
78
  "release:ci": "pnpm run check:pack-version && pnpm exec changeset publish",
78
- "release:local": "pnpm exec changeset version && pnpm run check:pack-version && pnpm exec changeset publish",
79
79
  "changeset": "changeset"
80
80
  }
81
81
  }