@tmmk/media-suite 0.1.2 → 0.1.3

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.
Files changed (2) hide show
  1. package/cordis.patch.yml +15 -4
  2. package/package.json +1 -1
package/cordis.patch.yml CHANGED
@@ -1,10 +1,21 @@
1
- # media-suite mounts only its own row. The provider packages are separate
2
- # bundles with their own patches: the plugin manager installs them alongside this
3
- # suite, and their bundle patches insert their rows. Re-inserting the same ids
4
- # here would collide with those patches, so this file deliberately does not.
1
+ # media-suite is the distribution shell: installing it must mount the provider
2
+ # rows too, because its providers arrive as plain npm dependencies and
3
+ # dependencies are NOT added to dsh.profile.bundles by `dsh plugin add`. Only
4
+ # bundle patches of packages listed in dsh.profile.bundles are applied, so the
5
+ # providers' own patches would never run. The suite therefore inserts all three
6
+ # rows itself.
5
7
  #
6
8
  # The suite has no config: where files land is a per-call choice, not a profile
7
9
  # setting.
8
10
  - insert:
9
11
  - id: media-suite
10
12
  name: '@tmmk/media-suite'
13
+ - id: media-qwen
14
+ name: '@tmmk/media-qwen'
15
+ - id: media-runninghub
16
+ name: '@tmmk/media-runninghub'
17
+ config:
18
+ surface: jobs
19
+ channel: lowprice
20
+ concurrency: 2
21
+ pollIntervalSeconds: 30
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tmmk/media-suite",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "type": "module",
5
5
  "main": "index.js",
6
6
  "engines": {