@intentius/chant 0.124.102 → 0.124.104
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/dist/audit/secrets.d.ts +6 -0
- package/dist/audit/secrets.js +9 -2
- package/dist/cli/commands/import-index.d.ts +15 -0
- package/dist/cli/commands/import-index.js +37 -3
- package/dist/cli/commands/onboard.js +8 -8
- package/dist/cli/handlers/lifecycle.js +6 -0
- package/dist/cli/handlers/release-config.d.ts +15 -0
- package/dist/cli/handlers/release-config.js +58 -0
- package/dist/cli/handlers/release-init.js +3 -1
- package/dist/cli/handlers/release.js +36 -3
- package/dist/cli/main.js +24 -3
- package/dist/cli/parse-args.js +12 -0
- package/dist/cli/registry.d.ts +4 -0
- package/dist/cli/release-commands/cut.js +3 -0
- package/dist/cloud-lister/kubernetes-components.js +1 -2
- package/dist/config-import.js +26 -4
- package/dist/config.d.ts +14 -0
- package/dist/config.js +4 -0
- package/dist/floor-table.data.js +13 -11
- package/dist/floor-table.js +3 -1
- package/dist/graph-refs.d.ts +9 -0
- package/dist/graph-refs.js +9 -7
- package/dist/lifecycle/cloud-index.d.ts +6 -0
- package/dist/lifecycle/cloud-index.js +32 -5
- package/dist/lifecycle/identity-match.d.ts +18 -2
- package/dist/lifecycle/identity-match.js +10 -5
- package/dist/lifecycle/index-drift.d.ts +13 -0
- package/dist/lifecycle/index-drift.js +21 -3
- package/dist/lifecycle/index-import.d.ts +15 -0
- package/dist/lifecycle/index-import.js +25 -2
- package/dist/lifecycle/index-join.d.ts +1 -1
- package/dist/lifecycle/index-join.js +1 -1
- package/dist/lifecycle/publish-declaration.d.ts +6 -0
- package/dist/lifecycle/publish-declaration.js +19 -3
- package/dist/lifecycle/publish-forge.d.ts +2 -0
- package/dist/lifecycle/publish-forge.js +3 -1
- package/dist/lifecycle/publish-helm.js +1 -2
- package/dist/lifecycle/publish-maven.js +1 -2
- package/dist/lifecycle/publish-npm.js +1 -1
- package/dist/lifecycle/publish-nuget.js +1 -2
- package/dist/lifecycle/publish-oci.d.ts +27 -0
- package/dist/lifecycle/publish-oci.js +63 -8
- package/dist/lifecycle/publish-rubygems.js +1 -2
- package/dist/lifecycle/release-artifacts.js +1 -2
- package/dist/lifecycle/release-changelog.d.ts +18 -5
- package/dist/lifecycle/release-changelog.js +22 -10
- package/dist/lifecycle/release-cut.d.ts +13 -1
- package/dist/lifecycle/release-cut.js +3 -0
- package/dist/lifecycle/release-images.d.ts +32 -2
- package/dist/lifecycle/release-images.js +70 -2
- package/dist/lifecycle/release-init-goreleaser-images.d.ts +21 -0
- package/dist/lifecycle/release-init-goreleaser-images.js +160 -0
- package/dist/lifecycle/release-init.d.ts +22 -0
- package/dist/lifecycle/release-init.js +96 -16
- package/dist/local-chant.d.ts +3 -0
- package/dist/local-chant.js +28 -2
- package/dist/release-floors.d.ts +10 -6
- package/dist/release-floors.js +10 -6
- package/dist/ts-loader.d.ts +12 -3
- package/dist/ts-loader.js +27 -11
- package/dist/wave-runtime.mjs +291 -290
- package/dist/workspace/catalog-edges.d.ts +22 -0
- package/dist/workspace/catalog-edges.js +23 -0
- package/dist/workspace/release-steps/goreleaser.d.ts +6 -3
- package/dist/workspace/release-steps/goreleaser.js +12 -6
- package/dist/workspace/release-toolchains.d.ts +6 -0
- package/dist/workspace/release-toolchains.js +8 -0
- package/dist/workspace/release-train-workflow.d.ts +39 -3
- package/dist/workspace/release-train-workflow.js +258 -9
- package/dist/workspace/release-train.js +5 -1
- package/dist/workspace/release-workflow.d.ts +37 -0
- package/dist/workspace/release-workflow.js +97 -16
- package/dist/workspace/train-artifacts.d.ts +107 -0
- package/dist/workspace/train-artifacts.js +238 -0
- package/dist/workspace/train-cut.d.ts +34 -1
- package/dist/workspace/train-cut.js +98 -14
- package/dist/workspace/train-publish.d.ts +9 -0
- package/dist/workspace/train-publish.js +27 -1
- package/package.json +2 -2
package/dist/release-floors.d.ts
CHANGED
|
@@ -13,11 +13,15 @@
|
|
|
13
13
|
* cut a version when any floor names a version that is neither a published
|
|
14
14
|
* release nor the one being cut.
|
|
15
15
|
*
|
|
16
|
-
* After the cut, a floor stays at the value it was released with.
|
|
17
|
-
* release
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
16
|
+
* After the cut, a floor stays at the value it was released with. The
|
|
17
|
+
* release tags say which release first carried a floor still on this
|
|
18
|
+
* constant, and core's prepack (`scripts/release-floors.ts --pack`) builds
|
|
19
|
+
* with each such floor written as that release, every other one and this
|
|
20
|
+
* constant as the version being packed, then puts the sources back (#5260).
|
|
21
|
+
* So a release train needs no commit between releases, and this constant can
|
|
22
|
+
* name a release that already shipped. `just release-floors --freeze
|
|
23
|
+
* <version>` writes those literals into the sources and moves this constant
|
|
24
|
+
* to the next patch (#4501), for a tree that reads plainly.
|
|
21
25
|
*
|
|
22
26
|
* A new floor is declared next to the code it gates, in that feature's own
|
|
23
27
|
* file, as `export const <NAME>_FLOOR = NEXT_RELEASE;` with NEXT_RELEASE
|
|
@@ -26,7 +30,7 @@
|
|
|
26
30
|
* files rather than to the end of this one. The floors below were declared
|
|
27
31
|
* here before that and keep the subpath they shipped under.
|
|
28
32
|
*/
|
|
29
|
-
export declare const NEXT_RELEASE = "0.124.
|
|
33
|
+
export declare const NEXT_RELEASE = "0.124.104";
|
|
30
34
|
/** The first chant with `chant dev local` and `chant dev bundle-check`, `@intentius/chant/local-chant` and `@intentius/chant/bundle-check` (`chantRuntimeTarget`, `chantExternalPlugin`, `checkBundle`): a product built against a chant checkout, and its bundle checked, without its own scripts (#4787). */
|
|
31
35
|
export declare const LOCAL_CHANT_FLOOR = "0.124.86";
|
|
32
36
|
/** The first chant with `chant workspace ref-gate` (pre-receive, pre-push, check, status, attach, install) and `refs` in `.chant/trust.json`, the checks a ref update needs evidence for (#4867). */
|
package/dist/release-floors.js
CHANGED
|
@@ -13,11 +13,15 @@
|
|
|
13
13
|
* cut a version when any floor names a version that is neither a published
|
|
14
14
|
* release nor the one being cut.
|
|
15
15
|
*
|
|
16
|
-
* After the cut, a floor stays at the value it was released with.
|
|
17
|
-
* release
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
16
|
+
* After the cut, a floor stays at the value it was released with. The
|
|
17
|
+
* release tags say which release first carried a floor still on this
|
|
18
|
+
* constant, and core's prepack (`scripts/release-floors.ts --pack`) builds
|
|
19
|
+
* with each such floor written as that release, every other one and this
|
|
20
|
+
* constant as the version being packed, then puts the sources back (#5260).
|
|
21
|
+
* So a release train needs no commit between releases, and this constant can
|
|
22
|
+
* name a release that already shipped. `just release-floors --freeze
|
|
23
|
+
* <version>` writes those literals into the sources and moves this constant
|
|
24
|
+
* to the next patch (#4501), for a tree that reads plainly.
|
|
21
25
|
*
|
|
22
26
|
* A new floor is declared next to the code it gates, in that feature's own
|
|
23
27
|
* file, as `export const <NAME>_FLOOR = NEXT_RELEASE;` with NEXT_RELEASE
|
|
@@ -26,7 +30,7 @@
|
|
|
26
30
|
* files rather than to the end of this one. The floors below were declared
|
|
27
31
|
* here before that and keep the subpath they shipped under.
|
|
28
32
|
*/
|
|
29
|
-
export const NEXT_RELEASE = "0.124.
|
|
33
|
+
export const NEXT_RELEASE = "0.124.104";
|
|
30
34
|
/** The first chant with `chant dev local` and `chant dev bundle-check`, `@intentius/chant/local-chant` and `@intentius/chant/bundle-check` (`chantRuntimeTarget`, `chantExternalPlugin`, `checkBundle`): a product built against a chant checkout, and its bundle checked, without its own scripts (#4787). */
|
|
31
35
|
export const LOCAL_CHANT_FLOOR = "0.124.86";
|
|
32
36
|
/** The first chant with `chant workspace ref-gate` (pre-receive, pre-push, check, status, attach, install) and `refs` in `.chant/trust.json`, the checks a ref update needs evidence for (#4867). */
|
package/dist/ts-loader.d.ts
CHANGED
|
@@ -50,15 +50,24 @@ export declare function chantPackageSourceTarget(specifier: string, parentPath:
|
|
|
50
50
|
* registration covers this process, so a caller that registers its own
|
|
51
51
|
* CommonJS hook from source knows not to add a second one.
|
|
52
52
|
*/
|
|
53
|
-
export declare function ensureTypeScriptLoader(): boolean;
|
|
53
|
+
export declare function ensureTypeScriptLoader(projectDir?: string): boolean;
|
|
54
|
+
/**
|
|
55
|
+
* #5263 — where tsx resolves from: chant's own install first, then the
|
|
56
|
+
* project's (`projectDir`, then the working directory). chant run through
|
|
57
|
+
* `npx @intentius/chant@<v>` lives in npx's cache, where tsx is not
|
|
58
|
+
* installed, while the project has it in its `node_modules`. Returns the
|
|
59
|
+
* path or URL to resolve from, or undefined when neither has tsx.
|
|
60
|
+
*/
|
|
61
|
+
export declare function tsxResolvedFrom(projectDir?: string): string | undefined;
|
|
54
62
|
/**
|
|
55
63
|
* Whether this process can load a TypeScript module such as
|
|
56
64
|
* `chant.config.ts`: always from source, where a loader already runs chant
|
|
57
|
-
* itself, and in the compiled CLI when tsx resolves from chant's install
|
|
65
|
+
* itself, and in the compiled CLI when tsx resolves from chant's install or
|
|
66
|
+
* the project's (#5263).
|
|
58
67
|
* Nothing is registered; `chant release init` asks before it writes a
|
|
59
68
|
* config it would have to read back.
|
|
60
69
|
*/
|
|
61
|
-
export declare function typeScriptLoaderAvailable(): boolean;
|
|
70
|
+
export declare function typeScriptLoaderAvailable(projectDir?: string): boolean;
|
|
62
71
|
/**
|
|
63
72
|
* #3981 — register tsx only when the module about to be imported is not
|
|
64
73
|
* JavaScript. `pathOrUrl` is the resolved module, a path or a file URL. A
|
package/dist/ts-loader.js
CHANGED
|
@@ -229,36 +229,52 @@ function installSourceResolution() {
|
|
|
229
229
|
* registration covers this process, so a caller that registers its own
|
|
230
230
|
* CommonJS hook from source knows not to add a second one.
|
|
231
231
|
*/
|
|
232
|
-
export function ensureTypeScriptLoader() {
|
|
232
|
+
export function ensureTypeScriptLoader(projectDir) {
|
|
233
233
|
const state = compiledState();
|
|
234
234
|
if (!state)
|
|
235
235
|
return false;
|
|
236
236
|
if (state.tsx)
|
|
237
237
|
return true;
|
|
238
|
-
const
|
|
238
|
+
const from = tsxResolvedFrom(projectDir) ?? import.meta.url;
|
|
239
|
+
const load = (specifier) => requireOptionalPeer("tsx", specifier, "run TypeScript", from);
|
|
239
240
|
load("tsx/cjs/api").register();
|
|
240
241
|
load("tsx/esm/api").register();
|
|
241
242
|
state.tsx = true;
|
|
242
243
|
return true;
|
|
243
244
|
}
|
|
245
|
+
/**
|
|
246
|
+
* #5263 — where tsx resolves from: chant's own install first, then the
|
|
247
|
+
* project's (`projectDir`, then the working directory). chant run through
|
|
248
|
+
* `npx @intentius/chant@<v>` lives in npx's cache, where tsx is not
|
|
249
|
+
* installed, while the project has it in its `node_modules`. Returns the
|
|
250
|
+
* path or URL to resolve from, or undefined when neither has tsx.
|
|
251
|
+
*/
|
|
252
|
+
export function tsxResolvedFrom(projectDir) {
|
|
253
|
+
const bases = [import.meta.url, ...[projectDir, process.cwd()].filter((d) => d !== undefined).map((d) => join(d, "package.json"))];
|
|
254
|
+
for (const base of bases) {
|
|
255
|
+
try {
|
|
256
|
+
nodeModule.createRequire(base).resolve("tsx/cjs/api");
|
|
257
|
+
return base;
|
|
258
|
+
}
|
|
259
|
+
catch {
|
|
260
|
+
// Not installed where this base resolves from.
|
|
261
|
+
}
|
|
262
|
+
}
|
|
263
|
+
return undefined;
|
|
264
|
+
}
|
|
244
265
|
/**
|
|
245
266
|
* Whether this process can load a TypeScript module such as
|
|
246
267
|
* `chant.config.ts`: always from source, where a loader already runs chant
|
|
247
|
-
* itself, and in the compiled CLI when tsx resolves from chant's install
|
|
268
|
+
* itself, and in the compiled CLI when tsx resolves from chant's install or
|
|
269
|
+
* the project's (#5263).
|
|
248
270
|
* Nothing is registered; `chant release init` asks before it writes a
|
|
249
271
|
* config it would have to read back.
|
|
250
272
|
*/
|
|
251
|
-
export function typeScriptLoaderAvailable() {
|
|
273
|
+
export function typeScriptLoaderAvailable(projectDir) {
|
|
252
274
|
const state = compiledState();
|
|
253
275
|
if (!state || state.tsx)
|
|
254
276
|
return true;
|
|
255
|
-
|
|
256
|
-
nodeModule.createRequire(import.meta.url).resolve("tsx/cjs/api");
|
|
257
|
-
return true;
|
|
258
|
-
}
|
|
259
|
-
catch {
|
|
260
|
-
return false;
|
|
261
|
-
}
|
|
277
|
+
return tsxResolvedFrom(projectDir) !== undefined;
|
|
262
278
|
}
|
|
263
279
|
/**
|
|
264
280
|
* #3981 — register tsx only when the module about to be imported is not
|