@codedrifters/configulator 0.0.467 → 0.0.469

package/lib/index.mjs

@@ -40697,7 +40697,7 @@ function resolveReactViteSiteProjectOutdir(packageName) {
 }
 
 // src/projects/typescript-project.ts
-import { typescript } from "projen";
+import { ReleasableCommits, typescript } from "projen";
 import {
   NodePackageManager as NodePackageManager2,
   Transform,
@@ -40706,6 +40706,27 @@ import {
 import { ReleaseTrigger } from "projen/lib/release";
 import { merge as merge2 } from "ts-deepmerge";
 
+// src/projects/changelog-types.ts
+var CHANGELOG_TYPES = [
+  { type: "feat", section: "Features" },
+  { type: "fix", section: "Bug Fixes" },
+  { type: "perf", section: "Performance Improvements" },
+  { type: "revert", section: "Reverts" },
+  { type: "refactor", section: "Code Refactoring" },
+  { type: "docs", section: "Documentation" },
+  { type: "test", section: "Tests" },
+  { type: "build", section: "Build System" },
+  { type: "ci", section: "Continuous Integration" },
+  { type: "style", section: "Styles" },
+  { type: "chore", section: "Miscellaneous Chores" }
+];
+function resolveVersionrcOptions(merged, userSupplied) {
+  if (!userSupplied?.types) {
+    return merged;
+  }
+  return { ...merged, types: userSupplied.types };
+}
+
 // src/projects/monorepo-project.ts
 import { WorkflowSteps } from "projen/lib/github";
 import {
@@ -42082,14 +42103,69 @@ var TypeScriptProject = class extends typescript.TypeScriptProject {
         } : {}
       },
       /**
-       * Only release when the package folder source content or package.json
-       * (version, dependencies) changes.
+       * Only release when the package's own sources or `package.json`
+       * (version, dependencies) change.
+       *
+       * Deliberately narrower than the `"."` pathspec the bump decision and
+       * the changelog use below. Widening this to `<outdir>/**` would make
+       * all three filters select exactly the same files, but it also makes
+       * every package-local edit releasable — a test-only change, or the
+       * `.projen/` regeneration that a sibling package's change produces. In
+       * this monorepo that regeneration is routine, so the aligned trigger
+       * publishes versions whose tarballs are byte-identical to the previous
+       * one.
+       *
+       * The asymmetry that remains is benign: a package-local commit outside
+       * `src` cannot start a release on its own, but is still described in
+       * the notes of the next release that something else triggers. Notes
+       * covering slightly more than the trigger is the right direction for
+       * the two to disagree in.
        */
       releaseTrigger: ReleaseTrigger.continuous({
         paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
-      })
+      }),
+      /**
+       * Scope the other two release filters to the package folder, the same
+       * slice of history the trigger above reads from.
+       *
+       * `versionrcOptions.path` reaches `commit-and-tag-version`, which
+       * forwards it to `conventional-changelog` as a `git log` pathspec —
+       * without it the changelog between two package-scoped tags spans every
+       * commit in the monorepo. `releasableCommits` appends the same pathspec
+       * to the command that decides whether to bump at all; without it a
+       * package with no relevant changes still cuts a release, just with an
+       * empty changelog.
+       *
+       * `"."` rather than `resolvedOutdir`: both commands run with their
+       * working directory already set to the package outdir. A single string
+       * is all `path` accepts — `git-raw-commits` splices it into `git log`
+       * as one argv entry (`push("--", path)`), so the pathspec cannot be a
+       * list, so it cannot be narrowed to `src` plus `package.json` to match
+       * the trigger exactly.
+       *
+       * `types` gives every conventional-commit type a visible section. The
+       * preset hides or discards everything but `feat` and `fix` by default,
+       * while still bumping for them, which is what makes a package-local
+       * churn release ship notes holding nothing but a version heading. See
+       * `CHANGELOG_TYPES`.
+       */
+      versionrcOptions: { path: ".", types: [...CHANGELOG_TYPES] },
+      releasableCommits: ReleasableCommits.everyCommit(".")
+    };
+    const mergedOptions = merge2(defaultOptions, userOptions);
+    const options = {
+      ...mergedOptions,
+      /**
+       * `ts-deepmerge` concatenates arrays, so a supplied changelog `types`
+       * arrives appended to `CHANGELOG_TYPES` — and the preset resolves each
+       * commit with `types.find(...)`, so our entry would win every lookup
+       * and the consumer's list would be inert. Replace, don't concatenate.
+       */
+      versionrcOptions: resolveVersionrcOptions(
+        mergedOptions.versionrcOptions,
+        userOptions.versionrcOptions
+      )
     };
-    const options = merge2(defaultOptions, userOptions);
     super(options);
     this.addDevDeps("@types/node@catalog:");
     this.tsconfig?.file.addOverride("compilerOptions.skipLibCheck", true);
@@ -42340,7 +42416,7 @@ var DEFAULT_FAVICON_SVG = `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0
 `;
 
 // src/projects/aws-cdk-project.ts
-import { awscdk, Dependencies } from "projen";
+import { awscdk, Dependencies, ReleasableCommits as ReleasableCommits2 } from "projen";
 import {
   NodePackageManager as NodePackageManager3,
   Transform as Transform2,
@@ -44235,14 +44311,58 @@ var AwsCdkProject = class extends awscdk.AwsCdkTypeScriptApp {
         cooldown: 7
       },
       /**
-       * Only release when the package source content or package.json changes.
+       * Only release when the package's own sources or `package.json`
+       * (version, dependencies) change.
+       *
+       * Deliberately narrower than the `"."` pathspec the bump decision and
+       * the changelog use below. Widening this to `<outdir>/**` would make
+       * all three filters select exactly the same files, but it also makes
+       * every package-local edit releasable — a test-only change, or the
+       * `.projen/` regeneration that a sibling package's change produces. In
+       * this monorepo that regeneration is routine, so the aligned trigger
+       * publishes versions whose tarballs are byte-identical to the previous
+       * one.
+       *
+       * The asymmetry that remains is benign: a package-local commit outside
+       * `src` cannot start a release on its own, but is still described in
+       * the notes of the next release that something else triggers. Notes
+       * covering slightly more than the trigger is the right direction for
+       * the two to disagree in.
        */
       releaseTrigger: ReleaseTrigger2.continuous({
         paths: [`${resolvedOutdir}/src/**`, `${resolvedOutdir}/package.json`]
-      })
+      }),
+      /**
+       * Scope the other two release filters to the package folder, the same
+       * slice of history the trigger above reads from.
+       *
+       * `versionrcOptions.path` reaches `commit-and-tag-version`, which
+       * forwards it to `conventional-changelog` as a `git log` pathspec —
+       * without it the changelog between two package-scoped tags spans every
+       * commit in the monorepo. `releasableCommits` appends the same pathspec
+       * to the command that decides whether to bump at all; without it a
+       * package with no relevant changes still cuts a release, just with an
+       * empty changelog.
+       *
+       * `"."` rather than `resolvedOutdir`: both commands run with their
+       * working directory already set to the package outdir. A single string
+       * is all `path` accepts — `git-raw-commits` splices it into `git log`
+       * as one argv entry (`push("--", path)`), so the pathspec cannot be a
+       * list, so it cannot be narrowed to `src` plus `package.json` to match
+       * the trigger exactly.
+       *
+       * `types` gives every conventional-commit type a visible section. The
+       * preset hides or discards everything but `feat` and `fix` by default,
+       * while still bumping for them, which is what makes a package-local
+       * churn release ship notes holding nothing but a version heading. See
+       * `CHANGELOG_TYPES`.
+       */
+      versionrcOptions: { path: ".", types: [...CHANGELOG_TYPES] },
+      releasableCommits: ReleasableCommits2.everyCommit(".")
     };
+    const mergedOptions = merge4(defaultOptions, userOptions);
     const options = {
-      ...merge4(defaultOptions, userOptions),
+      ...mergedOptions,
       /**
        * Both versions are the catalog's, resolved above — restate them after
        * the merge so a supplied option can never reintroduce a value the
@@ -44251,7 +44371,17 @@ var AwsCdkProject = class extends awscdk.AwsCdkTypeScriptApp {
        * projen.
        */
       cdkVersion,
-      constructsVersion
+      constructsVersion,
+      /**
+       * `ts-deepmerge` concatenates arrays, so a supplied changelog `types`
+       * arrives appended to `CHANGELOG_TYPES` — and the preset resolves each
+       * commit with `types.find(...)`, so our entry would win every lookup
+       * and the consumer's list would be inert. Replace, don't concatenate.
+       */
+      versionrcOptions: resolveVersionrcOptions(
+        mergedOptions.versionrcOptions,
+        userOptions.versionrcOptions
+      )
     };
     super(options);
     this.addDevDeps("@types/node@catalog:");
@@ -44872,6 +45002,7 @@ export {
   CDK_REQUIRE_APPROVAL,
   CDK_SYNTH_DEFAULTS_BY_STAGE,
   CDK_WATCH_DEFAULTS_BY_STAGE,
+  CHANGELOG_TYPES,
   CLAUDE_RULE_TARGET,
   COMPLETE_JOB_ID,
   CONVENTIONAL_COMMIT_TYPE_LABELS,
@@ -45214,6 +45345,7 @@ export {
   resolveTypeLabelForLabels,
   resolveTypeScriptProjectOutdir,
   resolveUnblockDependents,
+  resolveVersionrcOptions,
   runScan,
   slackBundle,
   softwareProfileBundle,