sysml-v2-lsp 0.17.0 → 0.18.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.
- package/CHANGELOG.md +17 -0
- package/dist/server/mcpServer.js +47 -22
- package/dist/server/server.js +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [0.18.0]
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- `specializationNames` field on `SysMLSymbol` to explicitly track names referenced via specialization relationships (`:>`, `:>>`, `specializes`, `subsets`, `subclassification`), distinct from feature typing
|
|
10
|
+
|
|
11
|
+
### Security
|
|
12
|
+
|
|
13
|
+
- Updated `fast-uri` to 3.1.2 — fixes path traversal via percent-encoded dot segments (GHSA-q3j6-qgpj-74h6) and host confusion via percent-encoded authority delimiters (GHSA-v39h-62p7-jpjc)
|
|
14
|
+
- Updated `hono` to 4.12.18 — fixes cache middleware cross-user leakage (GHSA-p77w-8qqv-26rm), CSS declaration injection in JSX SSR (GHSA-qp7p-654g-cw7p), JWT NumericDate claim bypass (GHSA-hm8q-7f3q-5f36), bodyLimit bypass for chunked requests (GHSA-9vqf-7f2p-gf9v), and unvalidated JSX tag names (GHSA-69xw-7hcm-h432)
|
|
15
|
+
- Updated `ip-address` to 10.2.0 and `express-rate-limit` to 8.5.1 — fixes XSS in Address6 HTML-emitting methods (GHSA-v2v4-37r5-5v8g)
|
|
16
|
+
- `specializes` key in `formatSymbol` MCP output, surfacing specialization names separately from `type`
|
|
17
|
+
- Regex fallback in specialization extraction now covers the `subsets` keyword (previously only `specializes`, `:>`, `:>>` were matched)
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
|
|
21
|
+
- **MCP API surface change**: the `type` field in `formatSymbol` output now contains feature-typing names only and excludes specialization names (which are surfaced via the new `specializes` key). Downstream MCP clients that previously read specialization targets from `type` should switch to reading the `specializes` field.
|
|
5
22
|
## [0.17.0]
|
|
6
23
|
|
|
7
24
|
### Added
|