airport-one-widgets 0.2.95 → 0.2.96

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 CHANGED
@@ -5,6 +5,33 @@
5
5
 
6
6
  **Fly My Airport FAB local demos:** with the widgets dev server running, open [`/demo/fly-my-airport-fab.html`](http://localhost:3001/demo/fly-my-airport-fab.html) (see root [`index.html`](./index.html) for the full demo menu).
7
7
 
8
+ ## Releases and channels
9
+
10
+ Airports load the bundle through `widgets.flymyairport.com`, which serves one
11
+ of two npm dist-tags ([ADR 0017](../../docs/decisions/0017-widget-release-channels.md)):
12
+
13
+ - **`latest`**: every airport.
14
+ - **`next`**: the pilot airports chosen in the portal under Platform Settings →
15
+ Release Management → Widget Releases, plus portal previews when that page
16
+ says so.
17
+
18
+ A merge that changes this package bumps `version` in `package.json` and
19
+ publishes through `CI | npm-widget | Publish`. The `WIDGET_NPM_DIST_TAG`
20
+ repository variable picks the channel: unset or `latest` reaches everyone,
21
+ `next` reaches only the pilot.
22
+
23
+ To pilot a release:
24
+
25
+ 1. Set `WIDGET_NPM_DIST_TAG` to `next`, then merge the version bump.
26
+ 2. Choose the pilot airports in the portal and save.
27
+ 3. When it looks right, run `CI | npm-widget | Promote` with that version and
28
+ channel `latest`.
29
+ 4. Clear the pilot list, and set `WIDGET_NPM_DIST_TAG` back to `latest` unless
30
+ another pilot is coming.
31
+
32
+ To roll back, run `CI | npm-widget | Promote` with the previous version and
33
+ channel `latest`. CDN caches take a few minutes to pick up either change.
34
+
8
35
  ## Airfare Search (v2)
9
36
 
10
37
  The v2 airfare-search widget is an explicit opt-in contract and does not alias from