[Compatibility] dsh-auto-mode 0.1.9 conflicts with the reserved "auto" permission preset on DSH 0.1.6-alpha.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authorization
Research direction
Start with the package's cordis.patch.yml, which is discovered from the profile bundle and contributes the auto permission preset. Reproduce the upgrade on DSH 0.1.6-alpha.1 with @nanmicoder/dsh-auto-mode@0.1.9 installed, then verify the package no longer collides with the reserved preset and the Web host boots successfully.
Written by the indexing model from the issue text.
Description
Observed behavior
A clean upgrade of an existing Web profile to DSH 0.1.6-alpha.1 aborts during profile composition before Web can start. The installed dsh-auto-mode package contributes a permission preset named auto; alpha.1 reserves that name for its built-in preset.
Steps to reproduce
- Start a Web profile on DSH 0.1.6-alpha.1.
- Keep @nanmicoder/dsh-auto-mode@0.1.9 installed (its cordis.patch.yml is discovered from the profile bundle).
- Boot dsh web.
- Observe the loader error.
Expected behavior
The plugin should either load without redefining the reserved preset or fail closed as an optional incompatible plugin without aborting the host. A compatible release should rename/remove its custom preset and advertise support for DSH 0.1.6-alpha.1.
Environment
DSH 0.1.6-alpha.1 (official release), @nanmicoder/dsh-auto-mode 0.1.9, Node v22.23.2, Linux x64.
DSH plugin context
The profile row was already disabled, but the package remained in dsh.profile.bundles. Removing the bundle entry makes the host boot, confirming the package patch is the collision source.
Error stack / details
failed to apply loader entry permission (@deepseek-ai/dsh-permission-presets): permission: "auto" is reserved and cannot name a configured preset
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 6
- Avg merge
- 9m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100