Skip to content

build(deps): bump the production-dependencies group across 1 directory with 12 updates - #416

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-dependencies-a92c0289bc
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/production-dependencies-a92c0289bc

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 12 updates in the / directory:

Package From To
@ant-design/icons 6.3.2 6.3.4
@fission-ai/openspec 1.11.0 1.13.0
@inquirer/ansi 2.0.7 2.0.8
@inquirer/core 12.0.1 12.0.3
@inquirer/figures 2.0.8 2.0.9
@inquirer/prompts 8.7.0 8.7.2
@inquirer/type 4.1.0 4.1.1
antd 6.6.2 6.6.3
dompurify 3.4.14 3.4.15
marked 18.0.11 18.0.12
mermaid 11.17.2 12.0.0
yaml 2.9.0 2.9.1

Updates @ant-design/icons from 6.3.2 to 6.3.4

Commits

Updates @fission-ai/openspec from 1.11.0 to 1.13.0

Release notes

Sourced from @​fission-ai/openspec's releases.

v1.13.0 - Apply warnings, safer archives

What's New in v1.13.0

Archive and the delta parser stop quietly changing or dropping what you wrote, and apply now tells you when a change has no specs.

New

  • Apply flags a change with no delta specs - openspec instructions apply used to report a change as ready whenever its tasks existed, even with no spec deltas at all, which is the state openspec validate rejects. It now warns in both text and --json, and names both ways out: write the specs, or declare skip_specs: true.

Improved

  • Explore finds your existing specs - Generated guidance never named openspec list --specs, so an agent asked to read the current specs enumerated in-flight changes instead and reported the step done against the wrong thing. Explore now lists the spec inventory beside the change list, and reads a capability with the store-aware command.
  • Init and update name the workflows your profile left out - A /opsx: command that was never installed used to read as a broken setup. Both commands now say which workflows are missing and how to add them.
  • Propose reads project context before planning - Context is loaded from the selected project or store root before any planning decision. In a directory with no OpenSpec root, propose stops without writing and offers to initialize rather than creating one silently.

Fixed

  • Archive no longer edits your fenced code - A requirement documenting a sample with two or more blank lines in a row had that sample rewritten on every archive. Blank-line tidying is now fence-aware, which matters for YAML, Python, and expected-output fixtures.
  • Removals and renames written with * or + now take effect - CommonMark allows all three bullet markers, but only - was read. A removal or rename written the other way matched nothing: validate passed, archive exited 0 reporting success, and the requirement stayed exactly as it was.
  • Every delta section applies, not just one copy - A file with two ## ADDED Requirements sections silently kept one of them, so archive applied less than was written and moved the change to the archive anyway. You do not have to repeat a header deliberately to hit this: a delta documenting OpenSpec's own syntax inside a fenced example produces the duplicate on its own.
  • Capabilities whose bullets wrap can be retired again - retire_capabilities refused any spec whose scenario bullets ran onto a second line, which is most of them in a repo that wraps prose at a column limit. Specs bulleted with + are covered too.
  • Update repairs damaged command files - openspec update decided a tool was current from its skill files alone, so a hand-edited or truncated command file left it printing "All 1 tool(s) up to date" and repairing nothing. It now compares command-file content as well.

New Contributors

Full Changelog: Fission-AI/OpenSpec@v1.12.0...v1.13.0

v1.12.0 - Findings Reports, SourceCraft

What's New in v1.12.0

OpenSpec v1.12.0 adds focused validation reports and SourceCraft support, while making planning, initialization, installation, and documentation more reliable.

New

  • Findings-only validation reports - Use openspec validate --report findings with explicit bulk scopes to show only errors, warnings, and informational findings while preserving full-run totals and exit codes.
  • SourceCraft Code Assistant support - Generate OpenSpec project skills and commands for the SourceCraft VS Code extension.

Improved

  • Code-grounded planning - Propose and fast-forward workflows now inspect relevant code, tests, and documentation before drafting artifacts.
  • Focused exploration - Explore mode asks dependency-aware questions, recommends defaults, and checks the repository before asking users for facts already present in the codebase.
  • Initialization reliability - Empty OpenSpec directories remain tracked in Git, and rerunning init safely restores missing markers.
  • Consistent restart guidance - Init and update now share accurate IDE restart hints, including when workflows are removed.
  • Documentation - Expanded archive, PowerShell completion, community showcase, spec behavior, analytics routing, and store-link guidance.

Fixed

  • Delta validation - Merge conflicts appear as informational findings without changing exit codes, filesystem read errors remain distinct from missing specs, and advisory preflight failures preserve the validation report.

... (truncated)

Changelog

Sourced from @​fission-ai/openspec's changelog.

1.13.0

Minor Changes

  • #1783 8ba4ac1 Thanks @​clay-good! - Apply now says when a change has no delta specs. Apply gates on the schema's apply.requires alone, so a change whose tasks.md was written ahead of its specs read as ready to implement even though it had no spec deltas at all — the state openspec validate rejects. openspec instructions apply now reports that gap as a warning (text and --json), naming both ways out: write the specs, or declare skip_specs: true. Changes that have specs, declare skip_specs, or are still blocked on their own required artifacts are unaffected.

    A blocked apply also names the whole chain now, not just the first hop: a change holding only a proposal reported Missing artifacts: tasks while the specs that tasks depends on were missing too, which reads as an instruction to write the tracking file straight from the proposal. The full build order is reported as missingPrerequisites in --json. The remedies these messages give are CLI commands (openspec instructions <artifact> --change <name>) rather than the openspec-continue-change skill, which the core profile never installs.

Patch Changes

  • #1798 aedf4d0 Thanks @​dwin-gharibi! - Stop archive rewriting the inside of fenced code blocks. The final assembly in buildUpdatedSpec collapsed runs of blank lines across the whole rebuilt document to tidy the seams between the slices it rejoins, but the pass was not fence-aware, so a requirement documenting a sample with two or more consecutive blank lines had that sample silently edited on archive, and edited again on every later archive. That matters wherever whitespace carries meaning: YAML block scalars, Python, expected-output fixtures, Markdown inside Markdown. Blank runs are now collapsed only outside fenced blocks, using the same buildCodeFenceMask every other structural pass in the module already used. Behavior outside fences is unchanged, including that only a truly empty line counts as blank, so a line of spaces is still never a collapse boundary. Fixes #1797.

  • #1800 fadac3e Thanks @​dwin-gharibi! - Read a removal or rename written with * or + as the operation it is. CommonMark opens a bullet list with -, * or +, but the bullet form of ## REMOVED Requirements and the FROM:/TO: lines of ## RENAMED Requirements both hardcoded -, so either other marker matched nothing at all. The operation then silently never happened: openspec validate reported the change valid, openspec archive exited 0 with "Specs updated successfully", and the requirement that was supposed to be deleted or renamed stayed exactly as it was. The change archived as complete, leaving the spec quietly disagreeing with the delta that was meant to update it. Both forms now accept [-*+], the FROM:/TO: bullet stays optional, and the plain ### Requirement: header form is unchanged. Fixes #1799.

  • #1802 8251763 Thanks @​dwin-gharibi! - Apply every delta section, not just one copy of each. A delta file that wrote the same header twice, two ## ADDED Requirements sections say, silently kept one of them: sections were collected into a record keyed by title, so a repeated title overwrote the earlier body, and the case-insensitive lookup returned only the first entry that folded to the target, so ## ADDED Requirements beside ## Added Requirements left the second unread. Every requirement under the discarded copy was gone before validation or the merge could see it, so openspec validate reported zero issues and openspec archive exited 0 having applied less than the author wrote, then moved the change to the archive with the live spec quietly diverging from what was reviewed. Sections are now kept as a list and every body whose title matches is read, each keeping its own line numbers so diagnostics still point at the right copy. Rename pairs are read per section, so a FROM: in one copy of the header can never pair with a TO: in another. An author does not have to repeat a header on purpose to hit this: a delta documenting OpenSpec's own syntax inside a fenced example produces the duplicate on its own. Fixes #1801.

  • #1657 6d2dbe6 Thanks @​clay-good! - Load project context before proposal planning, using the selected project or store root and honoring config precedence and validation limits. When no root exists, stop without writing files and offer initialization instead of creating an implicit root.

  • #1700 3915db7 Thanks @​clay-good! - Teach the generated guidance how to find and read a project's specs. openspec list --specs appeared in no generated skill, command, or artifact instruction, while openspec list --json (the in-flight change list) appeared throughout, so an agent asked to read the existing specs first enumerated changes instead and reported the step complete against the wrong object. The explore skill and command now list the spec inventory alongside the change list and say which is which, and the spec-driven proposal and specs instructions name the command where they ask for existing capabilities to be researched and for a delta's path to match an existing one. Both steps carry --store "<id>", and capabilities are read with openspec show "<spec-id>" --type spec --json --no-scenarios so the read resolves against the same root the listing came from. Fixes #1689.

    The filtered read is only an overview. Agents read relevant specs in full, including scenarios, before deciding what is already covered or what should change.

  • #1779 3c6d318 Thanks @​clay-good! - openspec init and openspec update now name the workflows your profile left out and how to add them, so a command that was never installed no longer reads as a broken setup.

  • #1808 d9e1a28 Thanks @​dwin-gharibi! - Stop openspec update reporting a tool up to date while a damaged command file sits on disk. The check read the generatedBy version marker in a tool's skill files alone, which proves only that the skill files came from this CLI and says nothing about the command files written beside them, so a hand-edited or truncated command file left update printing "All 1 tool(s) up to date" and repairing nothing; the file could be restored only by knowing to pass --force. A deleted command file was already detected, so the claim was false only for a damaged one. Update now also compares command-file content, using the comparison that already existed and was simply never consulted once a skill file supplied a version. Scoped to tools configured for both skills and commands, so the commands-only path is unchanged, and skipped when the delivery mode generates no commands for the tool. Fixes #1807.

  • #1782 c170dc7 Thanks @​clay-good! - Fix retire_capabilities refusing any spec whose scenario bullets wrap onto a second line. The continuation line was counted as content the merge could not account for, which blocked the retirement and suppressed the hint that names the marker (#1780). A spec bulleted with + is covered too: naming only - and * as list markers reported every one of its scenario bullets as unaccounted content, so that capability could not be retired at all either.

1.12.0

Minor Changes

  • #1171 44a39eb Thanks @​aleksandr4842! - Add SourceCraft Code Assistant as a supported tool for project skills and commands in its VS Code extension.

  • #1713 db03c6c Thanks @​Marzx13! - ### New Features

    • Add openspec validate --report findings for explicit bulk scopes. It returns only items with errors, warnings, or information while keeping full-run totals and exit codes. JSON output identifies the report and its scope; human output includes each finding's path and message. The default full report is unchanged.

Patch Changes

  • #1710 a4fcdbe Thanks @​ryandemelo! - Report delta merge conflicts during validation as informational findings, including in successful text reports, without changing validation exit codes. Preserve filesystem read errors so unreadable main specs are not mistaken for missing specs.

    Keep the validation report intact when the advisory merge preflight cannot resolve its inputs.

  • #1017 b976106 Thanks @​DanRioDev! - Improve explore mode guidance so it asks more useful dependency-aware questions, recommends defaults, and checks the codebase before asking for facts the repo can answer.

  • #1737 98bf53e Thanks @​clay-good! - Guide propose and fast-forward workflows to inspect relevant project code, tests, and documentation before drafting artifacts, so plans reflect the existing implementation instead of deferring basic discovery to implementation tasks.

  • #786 0296401 Thanks @​Br1an67! - Preserve empty OpenSpec directories in Git after initialization. Re-running init restores missing directory markers without overwriting existing files or following marker symlinks.

... (truncated)

Commits
  • 9d4e597 Version Packages (#1822)
  • e4e112d chore(deps): declare pnpm overrides only in pnpm-workspace.yaml (#1816)
  • aedf4d0 fix(archive): preserve blank lines inside code fences (#1798)
  • d9e1a28 fix(update): refresh generated files that drifted (#1808)
  • 8251763 fix(parser): apply every delta section header (#1802)
  • fadac3e fix(parser): accept all CommonMark list markers in deltas (#1800)
  • 3915db7 fix(guidance): teach the spec-inventory verb to generated guidance (#1700)
  • c170dc7 fix(archive): read a wrapped scenario bullet as one bullet (#1782)
  • 8ba4ac1 fix(apply): warn when a change is ready to implement with no specs (#1783)
  • 3c6d318 fix(init): name the workflows the profile left out (#1779)
  • Additional commits viewable in compare view

Updates @inquirer/ansi from 2.0.7 to 2.0.8

Release notes

Sourced from @​inquirer/ansi's releases.

@​inquirer/figures@​2.0.8

No source changes. Bumped to keep in lockstep with the @inquirer/* release train.

Commits
  • 5748bd9 chore: Publish new release
  • 269ae73 fix: pin @​inquirer/type exactly in published manifests
  • 927d6dd fix(@​inquirer/testing): keep keypress simulation working under TERM=dumb
  • 2d813b1 chore(deps): Bump @​humanfs/node from 0.16.6 to 0.16.8 (#2245)
  • 7affbc9 chore(deps-dev): Bump turbo from 2.10.9 to 2.10.11 in the build group (#2243)
  • 56db989 chore(deps-dev): Bump oxfmt in the formatting group (#2242)
  • 8e6bc3c chore(deps-dev): Bump the linting group with 2 updates (#2241)
  • 427b7a1 chore(deps-dev): Bump the testing group with 3 updates (#2240)
  • 51ac389 chore: Publish new release
  • 0f1718e feat(@​inquirer/password): add ctrl+t toggle to reveal password
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​inquirer/ansi since your current version.


Updates @inquirer/core from 12.0.1 to 12.0.3

Release notes

Sourced from @​inquirer/core's releases.

@​inquirer/core@​12.0.3

What's new

  • Fixed a race where keystrokes batched in the same tick as the key that settled a prompt could still reach useKeypress handlers after the prompt was done, cancelled, or aborted. Hook effects are now cleared in the synchronous settlement path (#2255, closes #1816).
  • Prompts created with an already-aborted signal now run the terminal cleanup (restore the cursor, close the readline interface, end the output stream) instead of leaking them (#2255).
Commits
  • cbdb34b chore: Publish new release
  • 8340d2d fix(@​inquirer/core): clear hook effects before settling prompts
  • 2475e07 test(@​inquirer/core): cover hook cleanup error semantics
  • 15cd8d3 fix(confirm): ignore surrounding whitespace in answers
  • 9cb0da6 chore(deps): Bump github/codeql-action/analyze from 4.37.7 to 4.37.9
  • 1c750bc chore(deps-dev): Bump the build group with 3 updates (#2251)
  • 81f1525 chore(deps-dev): Bump @​types/node in the types group (#2252)
  • 7c27f26 chore(deps-dev): Bump oxfmt in the formatting group (#2249)
  • 6119088 chore(deps): Bump github/codeql-action/init from 4.37.7 to 4.37.9 (#2250)
  • 0d167c0 chore(deps-dev): Bump the linting group with 4 updates (#2248)
  • Additional commits viewable in compare view

Updates @inquirer/figures from 2.0.8 to 2.0.9

Commits
  • 5748bd9 chore: Publish new release
  • 269ae73 fix: pin @​inquirer/type exactly in published manifests
  • 927d6dd fix(@​inquirer/testing): keep keypress simulation working under TERM=dumb
  • 2d813b1 chore(deps): Bump @​humanfs/node from 0.16.6 to 0.16.8 (#2245)
  • 7affbc9 chore(deps-dev): Bump turbo from 2.10.9 to 2.10.11 in the build group (#2243)
  • 56db989 chore(deps-dev): Bump oxfmt in the formatting group (#2242)
  • 8e6bc3c chore(deps-dev): Bump the linting group with 2 updates (#2241)
  • 427b7a1 chore(deps-dev): Bump the testing group with 3 updates (#2240)
  • 51ac389 chore: Publish new release
  • 0f1718e feat(@​inquirer/password): add ctrl+t toggle to reveal password
  • Additional commits viewable in compare view

Updates @inquirer/prompts from 8.7.0 to 8.7.2

Release notes

Sourced from @​inquirer/prompts's releases.

@​inquirer/prompts@​8.7.2

What's new

  • Fixed a race where keystrokes batched in the same tick as the key that settled a prompt could still reach keypress handlers after the prompt was done, cancelled, or aborted (@inquirer/core, #2255, closes #1816).
  • confirm() now trims surrounding whitespace from answers before matching yes/no keywords (@inquirer/confirm, #2254).

Included

  • @inquirer/checkbox@^5.2.5
  • @inquirer/confirm@^6.3.2
  • @inquirer/editor@^5.3.3
  • @inquirer/expand@^5.1.5
  • @inquirer/input@^5.1.6
  • @inquirer/number@^4.2.3
  • @inquirer/password@^5.2.2
  • @inquirer/rawlist@^5.3.5
  • @inquirer/search@^4.3.3
  • @inquirer/select@^5.2.5

@​inquirer/prompts@​8.7.1

What's new

  • All bundled prompts now pin @inquirer/type to an exact version in their published manifests. Since these type definitions leak into consumers' tsc runs, a semver range on the types-only dependency could break downstream TypeScript builds without any change to Inquirer.js itself (#2247, fixes #2244).

Included

  • @inquirer/checkbox@^5.2.4
  • @inquirer/confirm@^6.3.1
  • @inquirer/editor@^5.3.2
  • @inquirer/expand@^5.1.4
  • @inquirer/input@^5.1.5
  • @inquirer/number@^4.2.2
  • @inquirer/password@^5.2.1
  • @inquirer/rawlist@^5.3.4
  • @inquirer/search@^4.3.2
  • @inquirer/select@^5.2.4
Commits
  • cbdb34b chore: Publish new release
  • 8340d2d fix(@​inquirer/core): clear hook effects before settling prompts
  • 2475e07 test(@​inquirer/core): cover hook cleanup error semantics
  • 15cd8d3 fix(confirm): ignore surrounding whitespace in answers
  • 9cb0da6 chore(deps): Bump github/codeql-action/analyze from 4.37.7 to 4.37.9
  • 1c750bc chore(deps-dev): Bump the build group with 3 updates (#2251)
  • 81f1525 chore(deps-dev): Bump @​types/node in the types group (#2252)
  • 7c27f26 chore(deps-dev): Bump oxfmt in the formatting group (#2249)
  • 6119088 chore(deps): Bump github/codeql-action/init from 4.37.7 to 4.37.9 (#2250)
  • 0d167c0 chore(deps-dev): Bump the linting group with 4 updates (#2248)
  • Additional commits viewable in compare view

Updates @inquirer/type from 4.1.0 to 4.1.1

Commits
  • 5748bd9 chore: Publish new release
  • 269ae73 fix: pin @​inquirer/type exactly in published manifests
  • 927d6dd fix(@​inquirer/testing): keep keypress simulation working under TERM=dumb
  • 2d813b1 chore(deps): Bump @​humanfs/node from 0.16.6 to 0.16.8 (#2245)
  • 7affbc9 chore(deps-dev): Bump turbo from 2.10.9 to 2.10.11 in the build group (#2243)
  • 56db989 chore(deps-dev): Bump oxfmt in the formatting group (#2242)
  • 8e6bc3c chore(deps-dev): Bump the linting group with 2 updates (#2241)
  • 427b7a1 chore(deps-dev): Bump the testing group with 3 updates (#2240)
  • See full diff in compare view

Updates antd from 6.6.2 to 6.6.3

Release notes

Sourced from antd's releases.

6.6.3


... (truncated)

Changelog

Sourced from antd's changelog.

6.6.3

2026-09-07

Commits
  • 6b46530 docs: add changelog for 6.6.3 (#59239)
  • 9e9d2d5 fix(DatePicker): use German date formats (#59151)
  • 9ed4ef1 docs: explain SVG icon alignment in FAQ (#59238)
  • c0972ce docs: align API table defaults and versions between en-US and zh-CN (#59214)
  • c840fec docs: align open-state callback parameter names (#59236)
  • 23207f0 fix: stop mutating the mask config object passed by the user (#59233)
  • e825c6d docs: align getting started guides (#59188)
  • a170e43 chore(deps): update nearform-actions/github-action-notify-twitter digest to c...
  • a3f839f chore(deps): update dependency @​antfu/eslint-config to ~9.5.0 (#59227)
  • c4a242f chore(deps): update jest dependencies to v30.5.1 (#59228)
  • Additional commits viewable in

…y with 12 updates

Bumps the production-dependencies group with 12 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@ant-design/icons](https://github.com/ant-design/ant-design-icons) | `6.3.2` | `6.3.4` |
| [@fission-ai/openspec](https://github.com/Fission-AI/OpenSpec) | `1.11.0` | `1.13.0` |
| [@inquirer/ansi](https://github.com/SBoudrias/Inquirer.js) | `2.0.7` | `2.0.8` |
| [@inquirer/core](https://github.com/SBoudrias/Inquirer.js) | `12.0.1` | `12.0.3` |
| [@inquirer/figures](https://github.com/SBoudrias/Inquirer.js) | `2.0.8` | `2.0.9` |
| [@inquirer/prompts](https://github.com/SBoudrias/Inquirer.js) | `8.7.0` | `8.7.2` |
| [@inquirer/type](https://github.com/SBoudrias/Inquirer.js) | `4.1.0` | `4.1.1` |
| [antd](https://github.com/ant-design/ant-design) | `6.6.2` | `6.6.3` |
| [dompurify](https://github.com/cure53/DOMPurify) | `3.4.14` | `3.4.15` |
| [marked](https://github.com/markedjs/marked) | `18.0.11` | `18.0.12` |
| [mermaid](https://github.com/mermaid-js/mermaid) | `11.17.2` | `12.0.0` |
| [yaml](https://github.com/eemeli/yaml) | `2.9.0` | `2.9.1` |



Updates `@ant-design/icons` from 6.3.2 to 6.3.4
- [Commits](https://github.com/ant-design/ant-design-icons/commits)

Updates `@fission-ai/openspec` from 1.11.0 to 1.13.0
- [Release notes](https://github.com/Fission-AI/OpenSpec/releases)
- [Changelog](https://github.com/Fission-AI/OpenSpec/blob/main/CHANGELOG.md)
- [Commits](https://github.com/Fission-AI/OpenSpec/compare/v1.11.0...@fission-ai/openspec@1.13.0)

Updates `@inquirer/ansi` from 2.0.7 to 2.0.8
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/@inquirer/ansi@2.0.7...@inquirer/ansi@2.0.8)

Updates `@inquirer/core` from 12.0.1 to 12.0.3
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/@inquirer/core@12.0.1...@inquirer/core@12.0.3)

Updates `@inquirer/figures` from 2.0.8 to 2.0.9
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/@inquirer/figures@2.0.8...@inquirer/figures@2.0.9)

Updates `@inquirer/prompts` from 8.7.0 to 8.7.2
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/@inquirer/prompts@8.7.0...@inquirer/prompts@8.7.2)

Updates `@inquirer/type` from 4.1.0 to 4.1.1
- [Release notes](https://github.com/SBoudrias/Inquirer.js/releases)
- [Commits](https://github.com/SBoudrias/Inquirer.js/compare/@inquirer/type@4.1.0...@inquirer/type@4.1.1)

Updates `antd` from 6.6.2 to 6.6.3
- [Release notes](https://github.com/ant-design/ant-design/releases)
- [Changelog](https://github.com/ant-design/ant-design/blob/master/CHANGELOG.en-US.md)
- [Commits](ant-design/ant-design@6.6.2...6.6.3)

Updates `dompurify` from 3.4.14 to 3.4.15
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](cure53/DOMPurify@3.4.14...3.4.15)

Updates `marked` from 18.0.11 to 18.0.12
- [Release notes](https://github.com/markedjs/marked/releases)
- [Commits](markedjs/marked@v18.0.11...v18.0.12)

Updates `mermaid` from 11.17.2 to 12.0.0
- [Release notes](https://github.com/mermaid-js/mermaid/releases)
- [Commits](https://github.com/mermaid-js/mermaid/compare/mermaid@11.17.2...mermaid@12.0.0)

Updates `yaml` from 2.9.0 to 2.9.1
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.9.0...v2.9.1)

---
updated-dependencies:
- dependency-name: "@ant-design/icons"
  dependency-version: 6.3.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@fission-ai/openspec"
  dependency-version: 1.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: "@inquirer/ansi"
  dependency-version: 2.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@inquirer/core"
  dependency-version: 12.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@inquirer/figures"
  dependency-version: 2.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@inquirer/prompts"
  dependency-version: 8.7.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: "@inquirer/type"
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: antd
  dependency-version: 6.6.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: dompurify
  dependency-version: 3.4.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: marked
  dependency-version: 18.0.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: mermaid
  dependency-version: 12.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: yaml
  dependency-version: 2.9.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 14, 2026
@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 05db21af-c32f-4d0c-bf82-1528cd93bd1b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

👋 Thanks for opening your first PR to Comet, @dependabot[bot].

Before review, please make sure the PR title follows Conventional Commits, for example fix: handle project-scope init, and that the checklist in the PR template is up to date.

🧪 The most useful local checks are:

pnpm build
pnpm lint
pnpm format:check
pnpm test

🧰 If your change touches assets/skills/comet/scripts/, please also check script portability across macOS, Linux, and Windows Git Bash. Avoid sed -i, support both sha256sum and shasum -a 256, and guard optional grep pipelines with || true.

✨ We appreciate the contribution and will take a look as soon as we can.

@github-actions

Copy link
Copy Markdown

PR template needs attention

Please update this PR to match the current .github/PULL_REQUEST_TEMPLATE.md:

  • Missing template section: ## ✨ Summary
  • Missing template section: ## 🎯 Scope
  • Missing template section: ## 🧪 Testing
  • Missing template section: ## ✅ Checklist
  • Missing template section: ## 👀 Notes for Reviewers
  • Missing template item: CLI commands (init, status, doctor, update)
  • Missing template item: Core installer / platform detection
  • Missing template item: Comet skills (assets/skills/, assets/skills-zh/)
  • Missing template item: Comet shell scripts (assets/skills/comet/scripts/)
  • Missing template item: Tests / CI
  • Missing template item: Documentation / changelog
  • Missing template item: Other:
  • Missing template item: pnpm build
  • Missing template item: pnpm lint
  • Missing template item: pnpm run lint:architecture
  • Missing template item: pnpm format:check
  • Missing template item: pnpm test
  • Missing template item: pnpm test -- test/domains/comet-classic/comet-scripts.test.ts
  • Missing template item: Not run:
  • Missing template item: PR title follows Conventional Commits, for example fix: handle project-scope init
  • Missing template item: User-facing behavior is documented in README.md, README-zh.md, or CONTRIBUTING.md
  • Missing template item: CHANGELOG.md is updated when behavior changes
  • Missing template item: Skill changes were made in Chinese first when applicable, then synced to English
  • Missing template item: New scripts are included in assets/manifest.json and relevant tests
  • Missing template item: Shell scripts remain portable across macOS, Linux, and Windows Git Bash
  • Missing template item: No unrelated generated files or local artifacts are included
  • Checklist item is not checked: PR title follows Conventional Commits, for example fix: handle project-scope init
  • Checklist item is not checked: User-facing behavior is documented in README.md, README-zh.md, or CONTRIBUTING.md
  • Checklist item is not checked: CHANGELOG.md is updated when behavior changes
  • Checklist item is not checked: Skill changes were made in Chinese first when applicable, then synced to English
  • Checklist item is not checked: New scripts are included in assets/manifest.json and relevant tests
  • Checklist item is not checked: Shell scripts remain portable across macOS, Linux, and Windows Git Bash
  • Checklist item is not checked: No unrelated generated files or local artifacts are included

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants