@ndmspc/ndmspc-ui 1.4.3 → 1.4.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 +27 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -360,16 +360,40 @@ https://gitlab.com/api/v4/projects/ndmspc%2Fndmspc-ui/packages/generic/ndmspc-ui
|
|
|
360
360
|
|
|
361
361
|
(use `permalink/latest` in place of `<tag>` to always follow the newest release)
|
|
362
362
|
|
|
363
|
-
|
|
363
|
+
Three names describe what is downloadable:
|
|
364
|
+
|
|
365
|
+
| Name | What it serves | Moved by |
|
|
366
|
+
| ------------- | ----------------------------------------------- | ----------------------------------------- |
|
|
367
|
+
| `v1.4.5` | that tag's page, never overwritten | the tag's own pipeline |
|
|
368
|
+
| `v1.4-stable` | the newest `v1.4.x` page, pre-releases included | every `v1.4.*` tag (`release-stable`) |
|
|
369
|
+
| `next` | the newest `develop` build | every `develop` pipeline (`release-next`) |
|
|
370
|
+
|
|
371
|
+
`v1.4-stable` is what lets ndmspc release a 1.4 patch without ndmspc-ui being
|
|
372
|
+
tagged again: ndmspc asks for its own `v1.4.5`, falls back to `v1.4-stable`, and
|
|
373
|
+
only then to `next`. The slot is over-written in place (the previous package
|
|
374
|
+
version is deleted first), so downloading it always yields the latest page of
|
|
375
|
+
the series:
|
|
376
|
+
|
|
377
|
+
```
|
|
378
|
+
https://gitlab.com/api/v4/projects/ndmspc%2Fndmspc-ui/packages/generic/ndmspc-ui-page/v1.4-stable/ndmspc-ui-page.tar.gz
|
|
379
|
+
```
|
|
380
|
+
|
|
381
|
+
The page keeps the version of the tag it was built from (a `v1.4-stable` download
|
|
382
|
+
still shows `UI v1.4.5` in the user menu). Two consequences: rebuilding an older
|
|
383
|
+
series tag after a newer one moves the slot backwards (the last pipeline wins),
|
|
384
|
+
and `v1.5-stable` only appears with the first 1.5 tag. Pin an exact tag when a
|
|
385
|
+
byte-identical page matters.
|
|
386
|
+
|
|
387
|
+
For a rolling development pointer, every build of `develop` is published by the
|
|
364
388
|
`release-next` job to a single over-writable `next` slot in the Generic Package
|
|
365
|
-
Registry, so the URL always serves the latest `
|
|
389
|
+
Registry, so the URL always serves the latest `develop` page:
|
|
366
390
|
|
|
367
391
|
```
|
|
368
392
|
https://gitlab.com/api/v4/projects/ndmspc%2Fndmspc-ui/packages/generic/ndmspc-ui-page/next/ndmspc-ui-page.tar.gz
|
|
369
393
|
```
|
|
370
394
|
|
|
371
395
|
Point `_ui_url` above at that URL instead of the release downloads path to track
|
|
372
|
-
`
|
|
396
|
+
`develop` (substitute the numeric project id for `ndmspc%2Fndmspc-ui` if you prefer).
|
|
373
397
|
|
|
374
398
|
The archive extracts to a ready-to-serve web root (`index.html` + `assets/`).
|
|
375
399
|
A minimal CMake consumption looks like:
|