Skip to content

chore(compat): declare dsh.compat metadata - #75

Open
Shizuku-keop wants to merge 1 commit into
omdsh-dev:mainfrom
Shizuku-keop:main
Open

chore(compat): declare dsh.compat metadata#75
Shizuku-keop wants to merge 1 commit into
omdsh-dev:mainfrom
Shizuku-keop:main

Conversation

@Shizuku-keop

Copy link
Copy Markdown

Declares machine-readable compatibility metadata (dsh.compat) so tooling can
gate upgrades before they break:


  • equires: >=0.1.0-rc.7
  • \ ested: 0.1.0-rc.7 0.1.0-rc.8 0.1.1-rc.1 0.1.1-rc.2 (verified 2026-08-25 by dsh-compat-guard local matrix:
    install + full tree mount + clean exit on all four DSH versions)
  • \storageFormats: zstd-jsonl

Generated by dsh-compat-guard (https://github.com/Shizuku-keop/dsh-compat-guard).
Note: the tested list covers the plugin's API surface across DSH rc.7 -> rc.2;
the per-version results live in the compatibility registry (Blue-Whale-Harness/compat).

@Shizuku-keop

Copy link
Copy Markdown
Author

Hi maintainers — quick note from the author of dsh-compat-guard. This PR only adds machine-readable dsh.compat metadata (requires / tested / storageFormats) to package.json; no runtime behavior changes. The tested list was verified on 2026-08-25 via isolated install + full tree-mount smoke across DSH 0.1.0-rc.7, 0.1.0-rc.8, 0.1.1-rc.1 and 0.1.1-rc.2 (8/8 pass); per-version results also live in the community compat registry (Shizuku-keop/Blue-Whale-Harness/compat). Happy to adjust the range, kind value, or split the change — just say the word. Thanks for maintaining this!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant