@norskvideo/ctl-dev-kit 0.2.12 → 0.2.14

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.
@@ -1,6 +1,7 @@
1
1
  # Keep this product fresh against the ctl-* npm family: the test harness that
2
2
  # drives its smoke and integration tiers, the SDK, the foundation helpers and
3
- # the product-template schema.
3
+ # the product-template schema. Also the @norskvideo/moq-* family, the MoQ
4
+ # player stack the dashboards embed.
4
5
  #
5
6
  # sync-dev-kit already does this for the conventions package, and upgrade-latest
6
7
  # does it for the Norsk nightly line. Nothing did it for the rest, so the pins
@@ -109,14 +110,19 @@ jobs:
109
110
  token: ${{ secrets.CI_DISPATCH_TOKEN }}
110
111
  clean: true
111
112
 
112
- - name: Resolve the newest published ctl-* packages and rewrite the pins
113
+ - name: Resolve the newest published ctl-* and moq-* packages and rewrite the pins
113
114
  id: bump
114
115
  run: |
115
116
  set -euo pipefail
116
117
  reg="https://registry.npmjs.org"
117
118
  # The conventions package is deliberately absent: sync-dev-kit owns it,
118
119
  # lands it straight to main, and re-syncs the copied files with it.
119
- family="ctl-test-harness ctl-sdk ctl-foundation ctl-product-template-schema"
120
+ # The moq-* members are the @norskvideo fork of moq-dev/moq that the
121
+ # dashboards play through. They pin each other at one version, so all
122
+ # nine move together, including the ones a product only gets
123
+ # transitively. A minor bump of these (0.1 -> 0.2) is a breaking API
124
+ # change, which is what the red-gate draft PR is for.
125
+ family="ctl-test-harness ctl-sdk ctl-foundation ctl-product-template-schema moq-signals moq-flate moq-pattern moq-net moq-json moq-loc moq-msf moq-hang moq-watch"
120
126
 
121
127
  # Every tracked package.json, not just the root: a repo can pin the
122
128
  # same package in a nested workspace (playout pins the harness twice),
@@ -147,7 +153,7 @@ jobs:
147
153
  done
148
154
 
149
155
  if [ -z "$moved" ]; then
150
- echo "every ctl-* pin is already on its newest published version."
156
+ echo "every ctl-* and moq-* pin is already on its newest published version."
151
157
  echo "changed=0" >> "$GITHUB_OUTPUT"
152
158
  else
153
159
  echo "changed=1" >> "$GITHUB_OUTPUT"
@@ -175,14 +181,17 @@ jobs:
175
181
  # ^0.1.0 -- and `bun install` keeps whatever the lockfile already
176
182
  # resolved for a range it still satisfies. So probe sat on
177
183
  # ctl-foundation 0.1.14 from 2026-09-02 while 0.1.19 was current,
178
- # and this gate went red on `Export named 'parseProductRoleName' not
179
- # found in @norskvideo+ctl-foundation@0.1.14` -- which reads as the
180
- # bumped harness breaking the product, when it is a four-week-stale
181
- # transitive dep that no pin rewrite can reach.
184
+ # and this gate went red on an Export-named-parseProductRoleName-
185
+ # not-found from @norskvideo+ctl-foundation@0.1.14 -- which reads as
186
+ # the bumped harness breaking the product, when it is a four-week-
187
+ # stale transitive dep that no pin rewrite can reach. (No apostrophe
188
+ # anywhere in this step: the whole body is one bash -c string in
189
+ # single quotes, and conventions/workflow-quoting.test.ts fails on
190
+ # one.)
182
191
  #
183
192
  # Same family as the rewrite above, and deliberately named again
184
193
  # rather than shared: the two steps are separate shells.
185
- for pkg in ctl-test-harness ctl-sdk ctl-foundation ctl-product-template-schema; do
194
+ for pkg in ctl-test-harness ctl-sdk ctl-foundation ctl-product-template-schema moq-signals moq-flate moq-pattern moq-net moq-json moq-loc moq-msf moq-hang moq-watch; do
186
195
  for lock in $(git ls-files "*bun.lock"); do
187
196
  # Not every install root has every member, directly or
188
197
  # otherwise; bun says so and this moves on.
@@ -210,7 +219,7 @@ jobs:
210
219
  git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
211
220
  git checkout -B "$branch"
212
221
  git add -A
213
- git commit -m "chore: sync the ctl-* pins to their newest published versions"
222
+ git commit -m "chore: sync the ctl-* and moq-* pins to their newest published versions"
214
223
  # One branch, force-pushed: a daily schedule must refresh the standing
215
224
  # PR rather than accumulate a new one every morning.
216
225
  git push -f origin "$branch"
@@ -253,7 +262,7 @@ jobs:
253
262
  # documents; it was applied to one sibling convention and not its twin,
254
263
  # so this step failed with exit 127 in every product repo. curl and jq
255
264
  # ARE on the host PATH (the pin-resolve step above uses them).
256
- title="chore: sync the ctl-* pins to their newest published versions"
265
+ title="chore: sync the ctl-* and moq-* pins to their newest published versions"
257
266
  repo="${{ github.repository }}"; owner="${repo%%/*}"
258
267
  api="https://api.github.com/repos/$repo/pulls"
259
268
  curl_api=(--fail-with-body -sS -H "Authorization: Bearer $API_TOKEN" -H "Accept: application/vnd.github+json")
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@norskvideo/ctl-dev-kit",
3
- "version": "0.2.12",
3
+ "version": "0.2.14",
4
4
  "type": "module",
5
5
  "exports": {
6
6
  "./create-product": "./create-product/create-product.ts",