@codedrifters/configulator 0.0.467 → 0.0.468
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/lib/index.js +36 -2
- package/lib/index.js.map +1 -1
- package/lib/index.mjs +38 -4
- package/lib/index.mjs.map +1 -1
- package/package.json +1 -1
package/lib/index.js
CHANGED
|
@@ -42486,7 +42486,24 @@ var TypeScriptProject = class extends import_projen24.typescript.TypeScriptProje
|
|
|
42486
42486
|
*/
|
|
42487
42487
|
releaseTrigger: import_release.ReleaseTrigger.continuous({
|
|
42488
42488
|
paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
|
|
42489
|
-
})
|
|
42489
|
+
}),
|
|
42490
|
+
/**
|
|
42491
|
+
* Scope the other two release filters to the package as well, so the
|
|
42492
|
+
* whole release reads the same slice of history the trigger does.
|
|
42493
|
+
*
|
|
42494
|
+
* `versionrcOptions.path` reaches `commit-and-tag-version`, which
|
|
42495
|
+
* forwards it to `conventional-changelog` as a `git log` pathspec —
|
|
42496
|
+
* without it the changelog between two package-scoped tags spans every
|
|
42497
|
+
* commit in the monorepo. `releasableCommits` appends the same pathspec
|
|
42498
|
+
* to the command that decides whether to bump at all; without it a
|
|
42499
|
+
* package with no relevant changes still cuts a release, just with an
|
|
42500
|
+
* empty changelog.
|
|
42501
|
+
*
|
|
42502
|
+
* `"."` rather than `resolvedOutdir`: both commands run with their
|
|
42503
|
+
* working directory already set to the package outdir.
|
|
42504
|
+
*/
|
|
42505
|
+
versionrcOptions: { path: "." },
|
|
42506
|
+
releasableCommits: import_projen24.ReleasableCommits.everyCommit(".")
|
|
42490
42507
|
};
|
|
42491
42508
|
const options = (0, import_ts_deepmerge2.merge)(defaultOptions, userOptions);
|
|
42492
42509
|
super(options);
|
|
@@ -44634,7 +44651,24 @@ var AwsCdkProject = class extends import_projen31.awscdk.AwsCdkTypeScriptApp {
|
|
|
44634
44651
|
*/
|
|
44635
44652
|
releaseTrigger: import_release2.ReleaseTrigger.continuous({
|
|
44636
44653
|
paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
|
|
44637
|
-
})
|
|
44654
|
+
}),
|
|
44655
|
+
/**
|
|
44656
|
+
* Scope the other two release filters to the package as well, so the
|
|
44657
|
+
* whole release reads the same slice of history the trigger does.
|
|
44658
|
+
*
|
|
44659
|
+
* `versionrcOptions.path` reaches `commit-and-tag-version`, which
|
|
44660
|
+
* forwards it to `conventional-changelog` as a `git log` pathspec —
|
|
44661
|
+
* without it the changelog between two package-scoped tags spans every
|
|
44662
|
+
* commit in the monorepo. `releasableCommits` appends the same pathspec
|
|
44663
|
+
* to the command that decides whether to bump at all; without it a
|
|
44664
|
+
* package with no relevant changes still cuts a release, just with an
|
|
44665
|
+
* empty changelog.
|
|
44666
|
+
*
|
|
44667
|
+
* `"."` rather than `resolvedOutdir`: both commands run with their
|
|
44668
|
+
* working directory already set to the package outdir.
|
|
44669
|
+
*/
|
|
44670
|
+
versionrcOptions: { path: "." },
|
|
44671
|
+
releasableCommits: import_projen31.ReleasableCommits.everyCommit(".")
|
|
44638
44672
|
};
|
|
44639
44673
|
const options = {
|
|
44640
44674
|
...(0, import_ts_deepmerge4.merge)(defaultOptions, userOptions),
|