generatesaas 2.1.0 → 2.2.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/dist/index.js +139 -190
- package/dist/skill/content/SKILL.md +3 -3
- package/package.json +1 -1
|
@@ -216,8 +216,8 @@ Flipping it is a manifest edit + re-stage, exactly like option adoption in Step
|
|
|
216
216
|
> receiving updates from this project. Continue?
|
|
217
217
|
|
|
218
218
|
2. On confirmation, edit `.generatesaas/manifest.json`: set `"companionSource": "shared"`, add
|
|
219
|
-
`"companionRepoUrl"` (ask which repo; default `https://github.com/Duzbee/OpenCompanion`),
|
|
220
|
-
|
|
219
|
+
`"companionRepoUrl"` (ask which repo; default `https://github.com/Duzbee/OpenCompanion`), and
|
|
220
|
+
REMOVE `"companionName"`.
|
|
221
221
|
3. Re-run `npx generatesaas@latest update` to re-stage (append `auto` in Automatic mode), then
|
|
222
222
|
continue the normal flow. The CLI removes the now-stale `.generatesaas/companion-release.json`
|
|
223
223
|
on shared-source updates.
|
|
@@ -228,7 +228,7 @@ Flipping it is a manifest edit + re-stage, exactly like option adoption in Step
|
|
|
228
228
|
|
|
229
229
|
1. Edit `.generatesaas/manifest.json`: set `"companionSource": "vendored"`, add
|
|
230
230
|
`"companionName"` (ask; default: the title-cased project name + " Companion"), and REMOVE
|
|
231
|
-
`"companionRepoUrl"
|
|
231
|
+
`"companionRepoUrl"`.
|
|
232
232
|
2. Re-run `npx generatesaas@latest update` to re-stage. Applying vendors `apps/companion` + the
|
|
233
233
|
export pipeline, branded from the name.
|
|
234
234
|
3. Remind the user: the Companions page shows a publish-first state until they run
|