chore: update changelog generation configuration and scripts

- Refactored changelog generation logic into a dedicated CLI tool.
- Added example configuration for changelog generation.
- Updated `lerna.json` to improve package structure formatting.
- Enhanced `yarn.lock` with new dependencies for changelog generation.
- Improved documentation in `README.md` for programmatic API usage.
- Cleaned up and organized changelog generation scripts.

Author: maksimzinchuk

configs/release-config/README.md

@@ -96,6 +96,94 @@ This command:
 
 **Note:** This is typically a one-time operation during initial setup or migration.
 
+## Programmatic API for Changelog Generation
+
+You can also use the changelog generation functionality programmatically in your own scripts:
+
+### Using the CLI
+
+```bash
+# Install the package
+yarn add -D @vc-shell/release-config
+
+# Create a configuration file
+npx vc-generate-changelogs --help
+
+# Run with your config
+npx vc-generate-changelogs changelog-config.js
+```
+
+### Using the JavaScript API
+
+```typescript
+import { generateInitialChangelogs, PackageConfig } from "@vc-shell/release-config";
+
+const packages: PackageConfig[] = [
+  {
+    name: "framework",
+    path: "framework",
+    displayName: "Framework (@vc-shell/framework)"
+  },
+  {
+    name: "cli/api-client",
+    path: "cli/api-client",
+    displayName: "API Client Generator (@vc-shell/api-client-generator)"
+  },
+  // ... more packages
+];
+
+await generateInitialChangelogs({
+  packages,
+  rootDir: process.cwd(),           // Optional: root directory
+  generateRoot: true,                // Optional: generate root changelog
+  includeRootHeader: true            // Optional: include header in root changelog
+});
+```
+
+### Configuration File Format
+
+Create a `changelog-config.js` file:
+
+```javascript
+export default {
+  packages: [
+    {
+      name: "framework",
+      path: "framework",
+      displayName: "Framework (@vc-shell/framework)"
+    },
+    // ... more packages
+  ],
+  rootDir: process.cwd(),
+  generateRoot: true,
+  includeRootHeader: true,
+};
+```
+
+### Generating Only Root Changelog
+
+If you already have package changelogs and want to regenerate just the root one:
+
+```typescript
+import { generateRootChangelog } from "@vc-shell/release-config";
+
+await generateRootChangelog({
+  packages,
+  rootDir: process.cwd(),
+  includeRootHeader: true,
+});
+```
+
+### Use Cases
+
+This programmatic API is useful for:
+- **Custom monorepo structures** - Different from standard VC-Shell layout
+- **CI/CD pipelines** - Automated changelog generation
+- **Migration scripts** - One-time setup for new repositories
+- **Custom workflows** - Integration with other release tools
+
+See [changelog-config.example.js](./changelog-config.example.js) for a complete configuration example.
+
 ### Root CHANGELOG Format
 
 The root `CHANGELOG.md` groups changes by package for each version:

configs/release-config/changelog-config.example.js

@@ -0,0 +1,30 @@
+/**
+ * Example configuration for changelog generation
+ * Copy this file and adjust the packages array to match your project structure
+ */
+
+export default {
+  // Array of packages to generate changelogs for
+  packages: [
+    {
+      name: "framework",
+      path: "framework",
+      displayName: "Framework (@vc-shell/framework)"
+    },
+    {
+      name: "cli/api-client",
+      path: "cli/api-client",
+      displayName: "API Client Generator (@vc-shell/api-client-generator)"
+    },
+    // Add more packages as needed...
+  ],
+
+  // Optional: Root directory (defaults to process.cwd())
+  rootDir: process.cwd(),
+
+  // Optional: Generate consolidated root changelog (defaults to true)
+  generateRoot: true,
+
+  // Optional: Include header in root changelog (defaults to true)
+  includeRootHeader: true,
+};

configs/release-config/package.json

@@ -7,11 +7,15 @@
   "files": [
     "dist"
   ],
+  "bin": {
+    "vc-generate-changelogs": "./dist/cli-generate-changelogs.js"
+  },
   "scripts": {
     "build": "vite build"
   },
   "dependencies": {
     "chalk": "^2.4.2",
+    "conventional-changelog-cli": "^5.0.0",
     "cross-spawn": "^7.0.3",
     "lerna": "^9.0.0",
     "mri": "^1.2.0",

configs/release-config/src/cli-generate-changelogs.ts

@@ -0,0 +1,96 @@
+#!/usr/bin/env node
+import { generateInitialChangelogs, PackageConfig } from "./generate-changelogs.js";
+import { readFileSync } from "node:fs";
+import { resolve } from "node:path";
+import chalk from "chalk";
+
+/**
+ * CLI for generating initial changelogs
+ * Usage: vc-generate-changelogs [config-file]
+ *
+ * Config file should export an object with:
+ * {
+ *   packages: Array<{ name: string, path: string, displayName: string }>,
+ *   rootDir?: string,
+ *   generateRoot?: boolean,
+ *   includeRootHeader?: boolean
+ * }
+ */
+
+async function main() {
+  const args = process.argv.slice(2);
+
+  if (args.includes("--help") || args.includes("-h")) {
+    console.log(`
+${chalk.cyan("vc-generate-changelogs")} - Generate CHANGELOG.md files from git history
+
+${chalk.bold("USAGE:")}
+  vc-generate-changelogs [config-file]
+
+${chalk.bold("ARGUMENTS:")}
+  config-file    Path to configuration file (default: changelog-config.js)
+
+${chalk.bold("CONFIG FILE FORMAT:")}
+  The config file should export an object with the following structure:
+
+  export default {
+    packages: [
+      {
+        name: "framework",
+        path: "framework",
+        displayName: "Framework (@vc-shell/framework)"
+      },
+      // ... more packages
+    ],
+    rootDir: process.cwd(),           // Optional: root directory
+    generateRoot: true,                // Optional: generate root changelog
+    includeRootHeader: true            // Optional: include header in root changelog
+  };
+
+${chalk.bold("EXAMPLE:")}
+  vc-generate-changelogs changelog-config.js
+    `);
+    process.exit(0);
+  }
+
+  const configPath = args[0] || "changelog-config.js";
+  const resolvedPath = resolve(process.cwd(), configPath);
+
+  try {
+    console.log(chalk.blue(`📖 Loading config from ${resolvedPath}...`));
+
+    // Dynamic import for ESM support
+    const config = await import(resolvedPath);
+    const options = config.default || config;
+
+    if (!options.packages || !Array.isArray(options.packages)) {
+      console.error(chalk.red("\n❌ Error: Config must export an object with 'packages' array"));
+      console.error(chalk.yellow("\nExpected format:"));
+      console.error(chalk.gray("  export default { packages: [...] }"));
+      process.exit(1);
+    }
+
+    // Validate package configs
+    for (const pkg of options.packages) {
+      if (!pkg.name || !pkg.path || !pkg.displayName) {
+        console.error(chalk.red(`\n❌ Error: Invalid package config: ${JSON.stringify(pkg)}`));
+        console.error(chalk.yellow("\nEach package must have: name, path, displayName"));
+        process.exit(1);
+      }
+    }
+
+    await generateInitialChangelogs(options);
+  } catch (error) {
+    if ((error as NodeJS.ErrnoException).code === "MODULE_NOT_FOUND" ||
+        (error as NodeJS.ErrnoException).code === "ERR_MODULE_NOT_FOUND") {
+      console.error(chalk.red(`\n❌ Error: Config file not found: ${resolvedPath}`));
+      console.error(chalk.yellow("\nCreate a config file or specify a different path."));
+      console.error(chalk.gray("\nRun 'vc-generate-changelogs --help' for more information."));
+    } else {
+      console.error(chalk.red("\n❌ Error generating changelogs:"), error);
+    }
+    process.exit(1);
+  }
+}
+
+main();