psadt-deploy-skill 0.47.0 → 0.49.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/README.md +18 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -69,7 +69,7 @@ Thirteen phases, each owned by a script rather than by prose, so a step either p
|
|
|
69
69
|
|
|
70
70
|
| Phase | What happens | Owner |
|
|
71
71
|
|---|---|---|
|
|
72
|
-
| **0** Setup |
|
|
72
|
+
| **0** Setup | 14 prerequisite checks, GREEN/YELLOW/RED, `-Fix` provisions | `Initialize-PsadtSkill.ps1` |
|
|
73
73
|
| **1-2** Intake + research | blocker questions as clickable options; a local-evidence ladder (installed here? binary here? already written down?) answers what it can, and a research agent is dispatched only per question it leaves open | agent (gates 1-2) |
|
|
74
74
|
| **3** Scaffold | a generator writes launcher + detection + per-run log name + manifest | `New-MsiPackage` · `New-ExePackage` · `New-BrowserExtensionPackage` · `New-WindowsFeaturePackage` · `New-DriverPackage` |
|
|
75
75
|
| **4** Customize | all three hooks filled from the research, helpers in the Extensions module | agent |
|
|
@@ -103,7 +103,7 @@ the same app from disagreeing about their own version.
|
|
|
103
103
|
- **A dossier is produced every time**, uploaded or not: one self-contained bilingual HTML file with the
|
|
104
104
|
return-code map, the detection rule, the hooks, the test results - and a ready-to-paste Company-Portal
|
|
105
105
|
description.
|
|
106
|
-
- **
|
|
106
|
+
- **968 Pester tests**, including drift guards that fail when the documentation and the code disagree -
|
|
107
107
|
one of them reads the published landing page and compares its figures against this repository.
|
|
108
108
|
|
|
109
109
|
## Go deeper
|
|
@@ -121,7 +121,7 @@ the same app from disagreeing about their own version.
|
|
|
121
121
|
## Status
|
|
122
122
|
|
|
123
123
|
In active use for the full build → package → test → dossier workflow, with the direct Graph upload
|
|
124
|
-
verified against a live tenant. The helper scripts are covered by
|
|
124
|
+
verified against a live tenant. The helper scripts are covered by 968 Pester tests.
|
|
125
125
|
|
|
126
126
|
One open point, honestly: **the driver `pnputil` exit-code semantics are documented, not verified here.**
|
|
127
127
|
`0` / `259` / `3010` and the two `0xE...` failures come from Microsoft's documentation; confirming them
|
|
@@ -170,7 +170,21 @@ installed.
|
|
|
170
170
|
**[CHANGELOG.md](CHANGELOG.md)** carries the complete history, every release since 0.1.0, and nothing is
|
|
171
171
|
ever removed from it.
|
|
172
172
|
|
|
173
|
-
Latest: **0.
|
|
173
|
+
Latest: **0.49.0 - The second version of an app started from a blank sheet.** Everything learned while
|
|
174
|
+
packaging an application - the switches that took an afternoon, the uninstaller that has to be renamed
|
|
175
|
+
first, the app mutex, the leftovers, both decision gates - was recorded in the manifest and then never
|
|
176
|
+
read again, because every store is keyed by the installer hash and a new version has a new hash.
|
|
177
|
+
`Get-PsadtPriorPackage.ps1` finds the previous package by application identity instead and offers what it
|
|
178
|
+
learned for confirmation. Purely additive: nothing that passes today starts failing.
|
|
179
|
+
|
|
180
|
+
Previously: **0.48.0 - The figure guards only ever read the figures.** The landing page described a skill two
|
|
181
|
+
releases old, and the guards could not see it: every site assertion checked a number, never whether the
|
|
182
|
+
list behind it was complete. The engine tile correctly said 19 while the table under it showed 14 rows.
|
|
183
|
+
The pre-flight gate was described as ten checks and runs fourteen. Phase 9 still told the reader to wire
|
|
184
|
+
supersedence themselves. The page is corrected, three wrong statements in the repo with it, and the
|
|
185
|
+
guards now compare lists name-by-name instead of counting.
|
|
186
|
+
|
|
187
|
+
Previously: **0.47.0 - The supersedence this skill has been wiring may never have been wired.** The upload has
|
|
174
188
|
POSTed a supersedence relationship since 0.8.x, on a route that is reported not to exist, catching the
|
|
175
189
|
failure and printing a yellow line - so a chain that never took looked like a normal run. No test touched
|
|
176
190
|
any of it. The write now uses the `updateRelationships` action the admin center uses, merges onto the
|