@quikit/quikpilot-runner 7.0.6 → 8.2.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 +27 -27
- package/dist/index.js +601 -77
- package/dist/index.js.map +4 -4
- package/package.json +26 -26
package/README.md
CHANGED
|
@@ -1,27 +1,27 @@
|
|
|
1
|
-
# @quikit/quikpilot-runner
|
|
2
|
-
|
|
3
|
-
QuikPilot's CI runner. Invoked automatically by the `.github/workflows/quikpilot.yml` file QuikPilot
|
|
4
|
-
installs in an onboarded repository — it fetches the run's work packet, runs your setup/lint/test
|
|
5
|
-
commands, reports results to QuikTest, enforces the denied-path guardrail, commits, pushes, and
|
|
6
|
-
reports back to QuikTrack.
|
|
7
|
-
|
|
8
|
-
This package is not meant to be installed or run by hand. It exists so a fix to QuikPilot's runner
|
|
9
|
-
logic ships as a new package version rather than a new pull request into every onboarded repository
|
|
10
|
-
— the workflow file itself lives in your repository (QuikIT cannot update it directly), so it stays a
|
|
11
|
-
thin, ~25-line launcher that invokes an exact, pinned version of this package via `npx`.
|
|
12
|
-
|
|
13
|
-
It carries no secrets and needs none of your credentials: it authenticates to QuikTrack and to GitHub
|
|
14
|
-
using short-lived tokens exchanged at runtime, never a value baked into the workflow file or this
|
|
15
|
-
package.
|
|
16
|
-
|
|
17
|
-
## Versioning and support
|
|
18
|
-
|
|
19
|
-
Every workflow file pins an **exact** version of this package (`npx --yes
|
|
20
|
-
@quikit/quikpilot-runner@<version>`, never a range or `latest`) — a repository never picks up a new
|
|
21
|
-
release on its own. Older published versions are not removed from npm and keep working as long as a
|
|
22
|
-
repository's workflow file keeps pinning them; upgrading to a newer version only happens through a new
|
|
23
|
-
pull request into that repository (QuikTrack's "re-bootstrap" flow), never silently.
|
|
24
|
-
|
|
25
|
-
Releases follow [SemVer](https://semver.org/): a major version bump means the workflow file's own
|
|
26
|
-
shape changed (inputs, permissions) and requires a new pull request regardless of this package's
|
|
27
|
-
version; minor/patch releases are runner-logic fixes safe to pick up on the next re-bootstrap.
|
|
1
|
+
# @quikit/quikpilot-runner
|
|
2
|
+
|
|
3
|
+
QuikPilot's CI runner. Invoked automatically by the `.github/workflows/quikpilot.yml` file QuikPilot
|
|
4
|
+
installs in an onboarded repository — it fetches the run's work packet, runs your setup/lint/test
|
|
5
|
+
commands, reports results to QuikTest, enforces the denied-path guardrail, commits, pushes, and
|
|
6
|
+
reports back to QuikTrack.
|
|
7
|
+
|
|
8
|
+
This package is not meant to be installed or run by hand. It exists so a fix to QuikPilot's runner
|
|
9
|
+
logic ships as a new package version rather than a new pull request into every onboarded repository
|
|
10
|
+
— the workflow file itself lives in your repository (QuikIT cannot update it directly), so it stays a
|
|
11
|
+
thin, ~25-line launcher that invokes an exact, pinned version of this package via `npx`.
|
|
12
|
+
|
|
13
|
+
It carries no secrets and needs none of your credentials: it authenticates to QuikTrack and to GitHub
|
|
14
|
+
using short-lived tokens exchanged at runtime, never a value baked into the workflow file or this
|
|
15
|
+
package.
|
|
16
|
+
|
|
17
|
+
## Versioning and support
|
|
18
|
+
|
|
19
|
+
Every workflow file pins an **exact** version of this package (`npx --yes
|
|
20
|
+
@quikit/quikpilot-runner@<version>`, never a range or `latest`) — a repository never picks up a new
|
|
21
|
+
release on its own. Older published versions are not removed from npm and keep working as long as a
|
|
22
|
+
repository's workflow file keeps pinning them; upgrading to a newer version only happens through a new
|
|
23
|
+
pull request into that repository (QuikTrack's "re-bootstrap" flow), never silently.
|
|
24
|
+
|
|
25
|
+
Releases follow [SemVer](https://semver.org/): a major version bump means the workflow file's own
|
|
26
|
+
shape changed (inputs, permissions) and requires a new pull request regardless of this package's
|
|
27
|
+
version; minor/patch releases are runner-logic fixes safe to pick up on the next re-bootstrap.
|