psadt-deploy-skill 0.23.0 → 0.23.1
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/README.md +11 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -39,7 +39,7 @@ That installs the skill into `~/.claude/skills/psadt-deploy` and runs the setup
|
|
|
39
39
|
everything it can and names the handful of values only you can supply (see
|
|
40
40
|
[First-run setup](#first-run-setup)). Then open Claude Code in any folder and say what you want:
|
|
41
41
|
|
|
42
|
-
> *"
|
|
42
|
+
> *"Create the Win32 Intune package for 7-Zip 24.09"* — or *"package Notepad++ for Intune"*
|
|
43
43
|
|
|
44
44
|
The skill asks at most **four decision gates** (scope · deployment semantics · SYSTEM-test consent ·
|
|
45
45
|
upload confirmation). Everything else it researches and states as an assumption instead of asking.
|
|
@@ -217,7 +217,8 @@ pwsh "$env:USERPROFILE\.claude\skills\psadt-deploy\scripts\Initialize-PsadtSkill
|
|
|
217
217
|
|
|
218
218
|
`npx skills add pt1987/claude-code-psadt-skill` works too, since `SKILL.md` sits in the repository root.
|
|
219
219
|
|
|
220
|
-
|
|
220
|
+
No git on the machine? The installer falls back to the branch tarball and Windows' own `tar.exe`, so the
|
|
221
|
+
one-liner still works.
|
|
221
222
|
|
|
222
223
|
The skill activates automatically when you ask Claude Code to build an Intune package, or when you work in
|
|
223
224
|
a folder containing `Invoke-AppDeployToolkit.ps1`.
|
|
@@ -368,6 +369,14 @@ pre-flight fails on non-ASCII without a BOM), and anything that lands in a packa
|
|
|
368
369
|
Recent releases below; the complete history is in **[CHANGELOG.md](CHANGELOG.md)** (nothing is ever removed
|
|
369
370
|
from either).
|
|
370
371
|
|
|
372
|
+
### 0.23.1 - 04.09.2026
|
|
373
|
+
- **Fixed: two generators were broken since 0.21.0.** `New-BrowserExtensionPackage.ps1` and
|
|
374
|
+
`New-WindowsFeaturePackage.ps1` died at run time — the per-run `LogName` change had wedged a statement
|
|
375
|
+
into the template `Replace(...)` chain, which PowerShell parses as a property assignment with an empty
|
|
376
|
+
name. Valid syntax, so neither the parse check nor the source-inspecting tests could see it; it surfaced
|
|
377
|
+
the first time the whole chain ran against a real package. A guard in all four generator test suites now
|
|
378
|
+
fails on a broken chain, and the guard itself was verified against a broken and a good sample.
|
|
379
|
+
|
|
371
380
|
### 0.23.0 - 04.09.2026
|
|
372
381
|
- **`npx psadt-deploy-skill`.** One line installs or updates the skill into `~/.claude/skills/psadt-deploy`
|
|
373
382
|
and runs the setup doctor. Flags `--dir`, `--project`, `--ref`, `--no-setup`. Cloning to exactly the right
|