@quikit/quikpilot-runner 8.2.8 → 9.1.0
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 +17 -0
- package/dist/index.js +744 -64
- package/dist/index.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -25,3 +25,20 @@ pull request into that repository (QuikTrack's "re-bootstrap" flow), never silen
|
|
|
25
25
|
Releases follow [SemVer](https://semver.org/): a major version bump means the workflow file's own
|
|
26
26
|
shape changed (inputs, permissions) and requires a new pull request regardless of this package's
|
|
27
27
|
version; minor/patch releases are runner-logic fixes safe to pick up on the next re-bootstrap.
|
|
28
|
+
|
|
29
|
+
**9.1.0 — the code-writing step sees the files the changed file imports.** For every existing file a run changes (code or
|
|
30
|
+
test), the runner now reads that file's own imports (JavaScript and TypeScript, one hop, never what those files import)
|
|
31
|
+
and sends the repository files they point to as extra context. They come after the files targeting named and never in
|
|
32
|
+
place of them. Packages, path aliases (`@/…`), stylesheets and images are not followed; a denied path is never read; the
|
|
33
|
+
extra files share the existing size limits, and if the runtime still finds the context too large the call is retried
|
|
34
|
+
without them. The `codegen.context` log line now also carries `importedPaths`, what was skipped and why (`import: too
|
|
35
|
+
large`, `import: over budget`, `import: unreadable`, `import: denied`, `import: not in workspace`) and how many path
|
|
36
|
+
aliases were not followed. The workflow file is unchanged, so a repository on 9.0.0 picks this up with its next
|
|
37
|
+
"runner version" pull request.
|
|
38
|
+
|
|
39
|
+
**9.0.0 — a failed run keeps its files.** When a run fails after code generation, the runner writes the files it
|
|
40
|
+
generated, a copy of the last test report and a short `manifest.json` (run, targets, files, the reason it stopped;
|
|
41
|
+
no credentials) to `quikpilot-failure/`, and the workflow's new `Keep the files of a failed run` step uploads that folder
|
|
42
|
+
as the Actions artifact `quikpilot-failed-run` for 7 days. Nothing is added to a branch or a pull request. That step is
|
|
43
|
+
part of the workflow file, so this is a major version: a repository on an older workflow file keeps working and simply
|
|
44
|
+
does not upload, until its "update the workflow" pull request is merged.
|