create-grist-widget 0.2.4 → 0.2.5
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 +10 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -46,8 +46,16 @@ simplest way to get from zero to a deployed widget:
|
|
|
46
46
|
folder `/ (root)`. This can only be set once `gh-pages` exists, which is
|
|
47
47
|
why it's a step *after* the first push, not before.
|
|
48
48
|
|
|
49
|
-
Once that's saved,
|
|
50
|
-
|
|
49
|
+
Once that's saved, your widget is live at two URLs:
|
|
50
|
+
|
|
51
|
+
- `https://<owner>.github.io/<repo>/latest/` — mutable, always points at
|
|
52
|
+
whatever version was last released.
|
|
53
|
+
- `https://<owner>.github.io/<repo>/v<version>/` — immutable, e.g. `/v0.0.1/`;
|
|
54
|
+
this exact version, forever, even after later releases move `/latest/`.
|
|
55
|
+
|
|
56
|
+
Paste whichever one fits into Grist's custom widget URL field — `/latest/`
|
|
57
|
+
if you want the widget to update automatically as you release new
|
|
58
|
+
versions, or a pinned `/v<version>/` if you don't.
|
|
51
59
|
|
|
52
60
|
> If the very first workflow run fails with a permissions error pushing
|
|
53
61
|
> to `gh-pages`, your repo's default Actions token permissions are
|