@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.mjs CHANGED
@@ -40697,7 +40697,7 @@ function resolveReactViteSiteProjectOutdir(packageName) {
40697
40697
  }
40698
40698
 
40699
40699
  // src/projects/typescript-project.ts
40700
- import { typescript } from "projen";
40700
+ import { ReleasableCommits, typescript } from "projen";
40701
40701
  import {
40702
40702
  NodePackageManager as NodePackageManager2,
40703
40703
  Transform,
@@ -42087,7 +42087,24 @@ var TypeScriptProject = class extends typescript.TypeScriptProject {
42087
42087
  */
42088
42088
  releaseTrigger: ReleaseTrigger.continuous({
42089
42089
  paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
42090
- })
42090
+ }),
42091
+ /**
42092
+ * Scope the other two release filters to the package as well, so the
42093
+ * whole release reads the same slice of history the trigger does.
42094
+ *
42095
+ * `versionrcOptions.path` reaches `commit-and-tag-version`, which
42096
+ * forwards it to `conventional-changelog` as a `git log` pathspec —
42097
+ * without it the changelog between two package-scoped tags spans every
42098
+ * commit in the monorepo. `releasableCommits` appends the same pathspec
42099
+ * to the command that decides whether to bump at all; without it a
42100
+ * package with no relevant changes still cuts a release, just with an
42101
+ * empty changelog.
42102
+ *
42103
+ * `"."` rather than `resolvedOutdir`: both commands run with their
42104
+ * working directory already set to the package outdir.
42105
+ */
42106
+ versionrcOptions: { path: "." },
42107
+ releasableCommits: ReleasableCommits.everyCommit(".")
42091
42108
  };
42092
42109
  const options = merge2(defaultOptions, userOptions);
42093
42110
  super(options);
@@ -42340,7 +42357,7 @@ var DEFAULT_FAVICON_SVG = `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0
42340
42357
  `;
42341
42358
 
42342
42359
  // src/projects/aws-cdk-project.ts
42343
- import { awscdk, Dependencies } from "projen";
42360
+ import { awscdk, Dependencies, ReleasableCommits as ReleasableCommits2 } from "projen";
42344
42361
  import {
42345
42362
  NodePackageManager as NodePackageManager3,
42346
42363
  Transform as Transform2,
@@ -44239,7 +44256,24 @@ var AwsCdkProject = class extends awscdk.AwsCdkTypeScriptApp {
44239
44256
  */
44240
44257
  releaseTrigger: ReleaseTrigger2.continuous({
44241
44258
  paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
44242
- })
44259
+ }),
44260
+ /**
44261
+ * Scope the other two release filters to the package as well, so the
44262
+ * whole release reads the same slice of history the trigger does.
44263
+ *
44264
+ * `versionrcOptions.path` reaches `commit-and-tag-version`, which
44265
+ * forwards it to `conventional-changelog` as a `git log` pathspec —
44266
+ * without it the changelog between two package-scoped tags spans every
44267
+ * commit in the monorepo. `releasableCommits` appends the same pathspec
44268
+ * to the command that decides whether to bump at all; without it a
44269
+ * package with no relevant changes still cuts a release, just with an
44270
+ * empty changelog.
44271
+ *
44272
+ * `"."` rather than `resolvedOutdir`: both commands run with their
44273
+ * working directory already set to the package outdir.
44274
+ */
44275
+ versionrcOptions: { path: "." },
44276
+ releasableCommits: ReleasableCommits2.everyCommit(".")
44243
44277
  };
44244
44278
  const options = {
44245
44279
  ...merge4(defaultOptions, userOptions),