@steerprotocol/data-connector-loader 5.0.0-next.4 → 5.0.0-next.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 +14 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,6 +31,20 @@ change must be marked as such for the first prerelease of a new major version.
|
|
|
31
31
|
The npm package must authorize `next-publish.yml` as a trusted publisher before
|
|
32
32
|
that workflow can publish.
|
|
33
33
|
|
|
34
|
+
## CI checks
|
|
35
|
+
|
|
36
|
+
The shared `next-ci.yml` matrix verifies Node 22 and Node 24. Each job runs
|
|
37
|
+
`npm ci` (which builds CommonJS and ESM through `prepare`), tests, Biome,
|
|
38
|
+
and packed-consumer checks. Node 24 collects coverage during its test run;
|
|
39
|
+
coverage comments are posted on same-repository pull requests with write access.
|
|
40
|
+
Fork and Dependabot pull requests still run coverage without posting comments.
|
|
41
|
+
|
|
42
|
+
Pull requests and non-release branch pushes run the shared CI directly.
|
|
43
|
+
Pushes to `next` or `main` run it once through their release workflow, and
|
|
44
|
+
publishing waits for both Node jobs. The release workflow filenames remain
|
|
45
|
+
unchanged for npm trusted publishing. The packed-consumer check installs into
|
|
46
|
+
a fresh temporary directory while reusing npm's download cache.
|
|
47
|
+
|
|
34
48
|
## Block-pinned strategy execution (recommended)
|
|
35
49
|
|
|
36
50
|
Supply a resolved `SmartPoolExecutionContext` to `ExecutionApp.executeWithContext`.
|