@jpp-toolkit/plugin-changesets 0.0.11

package/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Julien Papini
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/index.d.mts

@@ -0,0 +1,116 @@
+import { Command } from "@jpp-toolkit/core";
+import * as _oclif_core_interfaces3 from "@oclif/core/interfaces";
+
+//#region src/changeset-command.d.ts
+declare abstract class ChangesetCommand extends Command {
+  protected _execChangeset(args?: string[]): Promise<void>;
+}
+//#endregion
+//#region src/add-changeset-command.d.ts
+declare class AddChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static flags: {
+    empty: _oclif_core_interfaces3.BooleanFlag<boolean>;
+    open: _oclif_core_interfaces3.BooleanFlag<boolean>;
+  };
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/init-changeset-command.d.ts
+declare class InitChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/pre-changeset-command.d.ts
+declare class PreChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static args: {
+    action: _oclif_core_interfaces3.Arg<string, Record<string, unknown>>;
+    tag: _oclif_core_interfaces3.Arg<string | undefined, Record<string, unknown>>;
+  };
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/publish-changeset-command.d.ts
+declare class PublishChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static flags: {
+    otp: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+    tag: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+    'no-git-tag': _oclif_core_interfaces3.BooleanFlag<boolean>;
+  };
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/status-changeset-command.d.ts
+declare class StatusChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static flags: {
+    verbose: _oclif_core_interfaces3.BooleanFlag<boolean>;
+    output: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+    since: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+  };
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/tag-changeset-command.d.ts
+declare class TagChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/version-changeset-command.d.ts
+declare class VersionChangesetCommand extends ChangesetCommand {
+  static summary: string;
+  static description: string;
+  static flags: {
+    ignore: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+    snapshot: _oclif_core_interfaces3.OptionFlag<string | undefined, _oclif_core_interfaces3.CustomOptions>;
+  };
+  static examples: {
+    description: string;
+    command: string;
+  }[];
+  run(): Promise<void>;
+}
+//#endregion
+//#region src/index.d.ts
+declare const commands: {
+  'changeset:init': typeof InitChangesetCommand;
+  'changeset:add': typeof AddChangesetCommand;
+  'changeset:version': typeof VersionChangesetCommand;
+  'changeset:publish': typeof PublishChangesetCommand;
+  'changeset:status': typeof StatusChangesetCommand;
+  'changeset:pre': typeof PreChangesetCommand;
+  'changeset:tag': typeof TagChangesetCommand;
+};
+//#endregion
+export { commands };
+//# sourceMappingURL=index.d.mts.map

package/dist/index.mjs

@@ -0,0 +1,317 @@
+import { createRequire } from "node:module";
+import { Args, Flags } from "@oclif/core";
+import path from "node:path";
+import { Command } from "@jpp-toolkit/core";
+import { findProjectRoot } from "@jpp-toolkit/utils";
+import { execa } from "execa";
+
+//#region src/changeset-command.ts
+const require = createRequire(import.meta.url);
+const CHANGESET_BIN = path.resolve(require.resolve("@changesets/cli/package.json"), "../bin.js");
+var ChangesetCommand = class extends Command {
+	async _execChangeset(args = []) {
+		if ((await execa(CHANGESET_BIN, args, {
+			cwd: findProjectRoot(),
+			stdio: "inherit",
+			reject: false
+		})).failed) process.exit(1);
+	}
+};
+
+//#endregion
+//#region src/add-changeset-command.ts
+var AddChangesetCommand = class AddChangesetCommand extends ChangesetCommand {
+	static summary = "Add a new changeset to the project.";
+	static description = `
+This is the main command people use to interact with the changesets.
+
+This command will ask you a series of questions, first about what packages you want to release,
+then what semver bump type for each package, then it will ask for a summary of the entire changeset.
+The final step will show the changeset it will generate and confirm that you want to add it.
+
+Once confirmed, the changeset will be written a Markdown file that contains the summary and YAML
+front matter which stores the packages that will be released and the semver bump types for them.
+`;
+	static flags = {
+		empty: Flags.boolean({
+			char: "e",
+			description: "Create an empty changeset without prompts.",
+			default: false
+		}),
+		open: Flags.boolean({
+			char: "o",
+			description: "Open the changeset in the default editor after creating it.",
+			default: false
+		})
+	};
+	static examples = [
+		{
+			description: "Add a new changeset to the project.",
+			command: "<%= config.bin %> <%= command.id %>"
+		},
+		{
+			description: "Add an empty changeset without any prompts.",
+			command: "<%= config.bin %> <%= command.id %> --empty"
+		},
+		{
+			description: "Add a new changeset and open it in the default editor.",
+			command: "<%= config.bin %> <%= command.id %> --open"
+		}
+	];
+	async run() {
+		const { flags } = await this.parse(AddChangesetCommand);
+		const args = ["add"];
+		if (flags.empty) args.push("--empty");
+		if (flags.open) args.push("--open");
+		await this._execChangeset(args);
+	}
+};
+
+//#endregion
+//#region src/init-changeset-command.ts
+var InitChangesetCommand = class extends ChangesetCommand {
+	static summary = "Sets up the .changeset folder.";
+	static description = `
+This command sets up the .changeset folder. It generates a readme and a config file.
+The config file includes the default options and comments on what these options represent.
+You should run this command once when you are setting up changesets.
+`;
+	static examples = [{
+		description: "Initialize changesets in your repository.",
+		command: "<%= config.bin %> <%= command.id %>"
+	}];
+	async run() {
+		await this._execChangeset(["init"]);
+	}
+};
+
+//#endregion
+//#region src/pre-changeset-command.ts
+var PreChangesetCommand = class PreChangesetCommand extends ChangesetCommand {
+	static summary = "Enters and exits pre-release mode for packages.";
+	static description = `
+The pre command enters and exits pre mode. The command does not do any actual versioning, when doing
+a pre-release, you should run changeset pre enter next(or a different tag, the tag is what is in
+versions and is the npm dist tag) and then do the normal release process with changeset version and
+changeset publish.
+`;
+	static args = {
+		action: Args.string({
+			name: "action",
+			required: true,
+			description: "The pre-release action to perform.",
+			options: ["enter", "exit"]
+		}),
+		tag: Args.string({
+			name: "tag",
+			required: false,
+			description: "The pre-release tag to use when entering pre-release mode."
+		})
+	};
+	static examples = [{
+		description: "Enter pre-release mode with the \"next\" tag.",
+		command: "<%= config.bin %> <%= command.id %> enter next"
+	}, {
+		description: "Exit pre-release mode.",
+		command: "<%= config.bin %> <%= command.id %> exit"
+	}];
+	async run() {
+		const { args } = await this.parse(PreChangesetCommand);
+		const commandArgs = ["pre", args.action];
+		if (args.action === "enter" && args.tag) commandArgs.push("--tag", args.tag);
+		await this._execChangeset(commandArgs);
+	}
+};
+
+//#endregion
+//#region src/publish-changeset-command.ts
+var PublishChangesetCommand = class PublishChangesetCommand extends ChangesetCommand {
+	static summary = "Publishes changes to npm, and creates git tags.";
+	static description = `
+This publishes changes to npm, and creates git tags. This works by going into each package, checking
+if the version it has in its package.json is published on npm, and if it is not, running the npm
+publish. If you are using pnpm as a package manager, this automatically detects it and uses pnpm
+publish instead.
+`;
+	static flags = {
+		"otp": Flags.string({
+			char: "o",
+			description: "One-time password for publishing to npm.",
+			required: false
+		}),
+		"tag": Flags.string({
+			char: "t",
+			description: "Tag to publish the package under.",
+			required: false
+		}),
+		"no-git-tag": Flags.boolean({
+			description: "Skip creating a git tag after publishing.",
+			required: false,
+			default: false
+		})
+	};
+	static examples = [
+		{
+			description: "Publish packages to npm and create git tags.",
+			command: "<%= config.bin %> <%= command.id %>"
+		},
+		{
+			description: "Publish packages with a one-time password.",
+			command: "<%= config.bin %> <%= command.id %> --otp 123456"
+		},
+		{
+			description: "Publish packages under a specific tag.",
+			command: "<%= config.bin %> <%= command.id %> --tag beta"
+		},
+		{
+			description: "Publish packages without creating git tags.",
+			command: "<%= config.bin %> <%= command.id %> --no-git-tag"
+		}
+	];
+	async run() {
+		const { flags } = await this.parse(PublishChangesetCommand);
+		const args = ["publish"];
+		if (flags.otp) args.push("--otp", flags.otp);
+		if (flags.tag) args.push("--tag", flags.tag);
+		if (flags["no-git-tag"]) args.push("--no-git-tag");
+		await this._execChangeset(args);
+	}
+};
+
+//#endregion
+//#region src/status-changeset-command.ts
+var StatusChangesetCommand = class StatusChangesetCommand extends ChangesetCommand {
+	static summary = "Provides information about the changesets that currently exist.";
+	static description = `
+The status command provides information about the changesets that currently exist. If there are no
+changesets present, it exits with an error status code.
+`;
+	static flags = {
+		verbose: Flags.boolean({
+			char: "v",
+			description: "Use if you want to know the new versions, and get a link to the relevant changeset summary.",
+			required: false,
+			default: false
+		}),
+		output: Flags.string({
+			char: "o",
+			description: "Allows you to write the JSON object of the status output for consumption by other tools, such as CI.",
+			required: false
+		}),
+		since: Flags.string({
+			char: "s",
+			description: "Only display information about changesets since a specific branch or git tag (such as main, or the git hash of latest).",
+			required: false
+		})
+	};
+	static examples = [
+		{
+			description: "Get the status of changesets in the project.",
+			command: "<%= config.bin %> <%= command.id %>"
+		},
+		{
+			description: "Get a verbose status of changesets, including new versions and links to summaries.",
+			command: "<%= config.bin %> <%= command.id %> --verbose"
+		},
+		{
+			description: "Output the status of changesets as a JSON object.",
+			command: "<%= config.bin %> <%= command.id %> --output status.json"
+		},
+		{
+			description: "Get the status of changesets since a specific branch or git tag.",
+			command: "<%= config.bin %> <%= command.id %> --since main"
+		}
+	];
+	async run() {
+		const { flags } = await this.parse(StatusChangesetCommand);
+		const args = ["status"];
+		if (flags.verbose) args.push("--verbose");
+		if (flags.output) args.push("--output", flags.output);
+		if (flags.since) args.push("--since", flags.since);
+		await this._execChangeset(args);
+	}
+};
+
+//#endregion
+//#region src/tag-changeset-command.ts
+var TagChangesetCommand = class extends ChangesetCommand {
+	static summary = "Creates git tags for the current version of all packages.";
+	static description = `
+The tag command creates git tags for the current version of all packages. The tags created are
+equivalent to those created by changeset publish, but the tag command does not publish anything to
+npm.
+
+This is helpful in situations where a different tool, such as pnpm publish -r, is used to publish
+packages instead of changeset. For situations where changeset publish is executed, running changeset
+tag is not needed.
+
+The git tags in monorepos are created in the format pkg-name@version-number and are based on the
+current version number of the package.json for each package. Note that in single-package
+repositories, the git tag will include v before the version number, for example, v1.0.0. It is
+expected that changeset version is run before changeset tag, so the package.json versions are
+updated before the git tags are created.
+`;
+	async run() {
+		await this._execChangeset(["tag"]);
+	}
+};
+
+//#endregion
+//#region src/version-changeset-command.ts
+var VersionChangesetCommand = class VersionChangesetCommand extends ChangesetCommand {
+	static summary = "Takes changesets that have been made and updates versions and dependencies of packages, as well as writing changelogs.";
+	static description = `
+This is one of two commands responsible for releasing packages. The version command takes changesets
+that have been made and updates versions and dependencies of packages, as well as writing
+changelogs. It is responsible for all file changes to versions before publishing to npm.
+`;
+	static flags = {
+		ignore: Flags.string({
+			char: "i",
+			description: "Comma-separated list of packages to ignore when versioning.",
+			required: false
+		}),
+		snapshot: Flags.string({
+			char: "s",
+			description: "Create snapshot versions with the given tag.",
+			required: false
+		})
+	};
+	static examples = [
+		{
+			description: "Version packages based on changesets.",
+			command: "<%= config.bin %> <%= command.id %>"
+		},
+		{
+			description: "Version packages while ignoring specific packages.",
+			command: "<%= config.bin %> <%= command.id %> --ignore package-a,package-b"
+		},
+		{
+			description: "Version packages with snapshot versions.",
+			command: "<%= config.bin %> <%= command.id %> --snapshot beta"
+		}
+	];
+	async run() {
+		const { flags } = await this.parse(VersionChangesetCommand);
+		const args = ["version"];
+		if (flags.ignore) args.push("--ignore", flags.ignore);
+		if (flags.snapshot) args.push("--snapshot", flags.snapshot);
+		await this._execChangeset(args);
+	}
+};
+
+//#endregion
+//#region src/index.ts
+const commands = {
+	"changeset:init": InitChangesetCommand,
+	"changeset:add": AddChangesetCommand,
+	"changeset:version": VersionChangesetCommand,
+	"changeset:publish": PublishChangesetCommand,
+	"changeset:status": StatusChangesetCommand,
+	"changeset:pre": PreChangesetCommand,
+	"changeset:tag": TagChangesetCommand
+};
+
+//#endregion
+export { commands };
+//# sourceMappingURL=index.mjs.map

package/dist/index.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.mjs","names":["args: string[]","commandArgs: string[]","args: string[]","args: string[]","args: string[]"],"sources":["../src/changeset-command.ts","../src/add-changeset-command.ts","../src/init-changeset-command.ts","../src/pre-changeset-command.ts","../src/publish-changeset-command.ts","../src/status-changeset-command.ts","../src/tag-changeset-command.ts","../src/version-changeset-command.ts","../src/index.ts"],"sourcesContent":["import { createRequire } from 'node:module';\nimport path from 'node:path';\n\nimport { Command } from '@jpp-toolkit/core';\nimport { findProjectRoot } from '@jpp-toolkit/utils';\nimport { execa } from 'execa';\n\nconst require = createRequire(import.meta.url);\n\nconst CHANGESET_BIN = path.resolve(require.resolve('@changesets/cli/package.json'), '../bin.js');\n\nexport abstract class ChangesetCommand extends Command {\n    protected async _execChangeset(args: string[] = []): Promise<void> {\n        const cwd = findProjectRoot();\n        const result = await execa(CHANGESET_BIN, args, { cwd, stdio: 'inherit', reject: false });\n\n        if (result.failed) process.exit(1);\n    }\n}\n","import { Flags } from '@oclif/core';\n\nimport { ChangesetCommand } from './changeset-command';\n\nexport class AddChangesetCommand extends ChangesetCommand {\n    static override summary = 'Add a new changeset to the project.';\n\n    static override description = `\nThis is the main command people use to interact with the changesets.\n\nThis command will ask you a series of questions, first about what packages you want to release,\nthen what semver bump type for each package, then it will ask for a summary of the entire changeset.\nThe final step will show the changeset it will generate and confirm that you want to add it.\n\nOnce confirmed, the changeset will be written a Markdown file that contains the summary and YAML\nfront matter which stores the packages that will be released and the semver bump types for them.\n`;\n\n    static override flags = {\n        empty: Flags.boolean({\n            char: 'e',\n            description: 'Create an empty changeset without prompts.',\n            default: false,\n        }),\n        open: Flags.boolean({\n            char: 'o',\n            description: 'Open the changeset in the default editor after creating it.',\n            default: false,\n        }),\n    };\n\n    static override examples = [\n        {\n            description: 'Add a new changeset to the project.',\n            command: '<%= config.bin %> <%= command.id %>',\n        },\n        {\n            description: 'Add an empty changeset without any prompts.',\n            command: '<%= config.bin %> <%= command.id %> --empty',\n        },\n        {\n            description: 'Add a new changeset and open it in the default editor.',\n            command: '<%= config.bin %> <%= command.id %> --open',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        const { flags } = await this.parse(AddChangesetCommand);\n\n        const args: string[] = ['add'];\n        if (flags.empty) args.push('--empty');\n        if (flags.open) args.push('--open');\n\n        await this._execChangeset(args);\n    }\n}\n","import { ChangesetCommand } from './changeset-command';\n\nexport class InitChangesetCommand extends ChangesetCommand {\n    static override summary = 'Sets up the .changeset folder.';\n\n    static override description = `\nThis command sets up the .changeset folder. It generates a readme and a config file.\nThe config file includes the default options and comments on what these options represent.\nYou should run this command once when you are setting up changesets.\n`;\n\n    static override examples = [\n        {\n            description: 'Initialize changesets in your repository.',\n            command: '<%= config.bin %> <%= command.id %>',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        await this._execChangeset(['init']);\n    }\n}\n","import { Args } from '@oclif/core';\n\nimport { ChangesetCommand } from './changeset-command';\n\nexport class PreChangesetCommand extends ChangesetCommand {\n    static override summary = 'Enters and exits pre-release mode for packages.';\n\n    static override description = `\nThe pre command enters and exits pre mode. The command does not do any actual versioning, when doing\na pre-release, you should run changeset pre enter next(or a different tag, the tag is what is in\nversions and is the npm dist tag) and then do the normal release process with changeset version and\nchangeset publish.\n`;\n\n    static override args = {\n        action: Args.string({\n            name: 'action',\n            required: true,\n            description: 'The pre-release action to perform.',\n            options: ['enter', 'exit'],\n        }),\n        tag: Args.string({\n            name: 'tag',\n            required: false,\n            description: 'The pre-release tag to use when entering pre-release mode.',\n        }),\n    };\n\n    static override examples = [\n        {\n            description: 'Enter pre-release mode with the \"next\" tag.',\n            command: '<%= config.bin %> <%= command.id %> enter next',\n        },\n        {\n            description: 'Exit pre-release mode.',\n            command: '<%= config.bin %> <%= command.id %> exit',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        const { args } = await this.parse(PreChangesetCommand);\n\n        const commandArgs: string[] = ['pre', args.action];\n        if (args.action === 'enter' && args.tag) commandArgs.push('--tag', args.tag);\n\n        await this._execChangeset(commandArgs);\n    }\n}\n","import { Flags } from '@oclif/core';\n\nimport { ChangesetCommand } from './changeset-command';\n\nexport class PublishChangesetCommand extends ChangesetCommand {\n    static override summary = 'Publishes changes to npm, and creates git tags.';\n\n    static override description = `\nThis publishes changes to npm, and creates git tags. This works by going into each package, checking\nif the version it has in its package.json is published on npm, and if it is not, running the npm\npublish. If you are using pnpm as a package manager, this automatically detects it and uses pnpm\npublish instead.\n`;\n\n    static override flags = {\n        'otp': Flags.string({\n            char: 'o',\n            description: 'One-time password for publishing to npm.',\n            required: false,\n        }),\n        'tag': Flags.string({\n            char: 't',\n            description: 'Tag to publish the package under.',\n            required: false,\n        }),\n        'no-git-tag': Flags.boolean({\n            description: 'Skip creating a git tag after publishing.',\n            required: false,\n            default: false,\n        }),\n    };\n\n    static override examples = [\n        {\n            description: 'Publish packages to npm and create git tags.',\n            command: '<%= config.bin %> <%= command.id %>',\n        },\n        {\n            description: 'Publish packages with a one-time password.',\n            command: '<%= config.bin %> <%= command.id %> --otp 123456',\n        },\n        {\n            description: 'Publish packages under a specific tag.',\n            command: '<%= config.bin %> <%= command.id %> --tag beta',\n        },\n        {\n            description: 'Publish packages without creating git tags.',\n            command: '<%= config.bin %> <%= command.id %> --no-git-tag',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        const { flags } = await this.parse(PublishChangesetCommand);\n\n        const args: string[] = ['publish'];\n        if (flags.otp) args.push('--otp', flags.otp);\n        if (flags.tag) args.push('--tag', flags.tag);\n        if (flags['no-git-tag']) args.push('--no-git-tag');\n\n        await this._execChangeset(args);\n    }\n}\n","import { Flags } from '@oclif/core';\n\nimport { ChangesetCommand } from './changeset-command';\n\nexport class StatusChangesetCommand extends ChangesetCommand {\n    static override summary = 'Provides information about the changesets that currently exist.';\n\n    static override description = `\nThe status command provides information about the changesets that currently exist. If there are no\nchangesets present, it exits with an error status code.\n`;\n\n    static override flags = {\n        verbose: Flags.boolean({\n            char: 'v',\n            description:\n                'Use if you want to know the new versions, and get a link to the relevant changeset summary.',\n            required: false,\n            default: false,\n        }),\n        output: Flags.string({\n            char: 'o',\n            description:\n                'Allows you to write the JSON object of the status output for consumption by other tools, such as CI.',\n            required: false,\n        }),\n        since: Flags.string({\n            char: 's',\n            description:\n                'Only display information about changesets since a specific branch or git tag (such as main, or the git hash of latest).',\n            required: false,\n        }),\n    };\n\n    static override examples = [\n        {\n            description: 'Get the status of changesets in the project.',\n            command: '<%= config.bin %> <%= command.id %>',\n        },\n        {\n            description:\n                'Get a verbose status of changesets, including new versions and links to summaries.',\n            command: '<%= config.bin %> <%= command.id %> --verbose',\n        },\n        {\n            description: 'Output the status of changesets as a JSON object.',\n            command: '<%= config.bin %> <%= command.id %> --output status.json',\n        },\n        {\n            description: 'Get the status of changesets since a specific branch or git tag.',\n            command: '<%= config.bin %> <%= command.id %> --since main',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        const { flags } = await this.parse(StatusChangesetCommand);\n\n        const args: string[] = ['status'];\n        if (flags.verbose) args.push('--verbose');\n        if (flags.output) args.push('--output', flags.output);\n        if (flags.since) args.push('--since', flags.since);\n\n        await this._execChangeset(args);\n    }\n}\n","import { ChangesetCommand } from './changeset-command';\n\nexport class TagChangesetCommand extends ChangesetCommand {\n    static override summary = 'Creates git tags for the current version of all packages.';\n\n    static override description = `\nThe tag command creates git tags for the current version of all packages. The tags created are\nequivalent to those created by changeset publish, but the tag command does not publish anything to\nnpm.\n\nThis is helpful in situations where a different tool, such as pnpm publish -r, is used to publish\npackages instead of changeset. For situations where changeset publish is executed, running changeset\ntag is not needed.\n\nThe git tags in monorepos are created in the format pkg-name@version-number and are based on the\ncurrent version number of the package.json for each package. Note that in single-package\nrepositories, the git tag will include v before the version number, for example, v1.0.0. It is\nexpected that changeset version is run before changeset tag, so the package.json versions are\nupdated before the git tags are created.\n`;\n\n    public async run(): Promise<void> {\n        await this._execChangeset(['tag']);\n    }\n}\n","import { Flags } from '@oclif/core';\n\nimport { ChangesetCommand } from './changeset-command';\n\nexport class VersionChangesetCommand extends ChangesetCommand {\n    static override summary =\n        'Takes changesets that have been made and updates versions and dependencies of packages, as well as writing changelogs.';\n\n    static override description = `\nThis is one of two commands responsible for releasing packages. The version command takes changesets\nthat have been made and updates versions and dependencies of packages, as well as writing\nchangelogs. It is responsible for all file changes to versions before publishing to npm.\n`;\n\n    static override flags = {\n        ignore: Flags.string({\n            char: 'i',\n            description: 'Comma-separated list of packages to ignore when versioning.',\n            required: false,\n        }),\n        snapshot: Flags.string({\n            char: 's',\n            description: 'Create snapshot versions with the given tag.',\n            required: false,\n        }),\n    };\n\n    static override examples = [\n        {\n            description: 'Version packages based on changesets.',\n            command: '<%= config.bin %> <%= command.id %>',\n        },\n        {\n            description: 'Version packages while ignoring specific packages.',\n            command: '<%= config.bin %> <%= command.id %> --ignore package-a,package-b',\n        },\n        {\n            description: 'Version packages with snapshot versions.',\n            command: '<%= config.bin %> <%= command.id %> --snapshot beta',\n        },\n    ];\n\n    public async run(): Promise<void> {\n        const { flags } = await this.parse(VersionChangesetCommand);\n\n        const args: string[] = ['version'];\n        if (flags.ignore) args.push('--ignore', flags.ignore);\n        if (flags.snapshot) args.push('--snapshot', flags.snapshot);\n\n        await this._execChangeset(args);\n    }\n}\n","import { AddChangesetCommand } from './add-changeset-command';\nimport { InitChangesetCommand } from './init-changeset-command';\nimport { PreChangesetCommand } from './pre-changeset-command';\nimport { PublishChangesetCommand } from './publish-changeset-command';\nimport { StatusChangesetCommand } from './status-changeset-command';\nimport { TagChangesetCommand } from './tag-changeset-command';\nimport { VersionChangesetCommand } from './version-changeset-command';\n\nexport const commands = {\n    'changeset:init': InitChangesetCommand,\n    'changeset:add': AddChangesetCommand,\n    'changeset:version': VersionChangesetCommand,\n    'changeset:publish': PublishChangesetCommand,\n    'changeset:status': StatusChangesetCommand,\n    'changeset:pre': PreChangesetCommand,\n    'changeset:tag': TagChangesetCommand,\n};\n"],"mappings":";;;;;;;;AAOA,MAAM,UAAU,cAAc,OAAO,KAAK,IAAI;AAE9C,MAAM,gBAAgB,KAAK,QAAQ,QAAQ,QAAQ,+BAA+B,EAAE,YAAY;AAEhG,IAAsB,mBAAtB,cAA+C,QAAQ;CACnD,MAAgB,eAAe,OAAiB,EAAE,EAAiB;AAI/D,OAFe,MAAM,MAAM,eAAe,MAAM;GAAE,KADtC,iBAAiB;GAC0B,OAAO;GAAW,QAAQ;GAAO,CAAC,EAE9E,OAAQ,SAAQ,KAAK,EAAE;;;;;;ACZ1C,IAAa,sBAAb,MAAa,4BAA4B,iBAAiB;CACtD,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;;;;;;;CAW9B,OAAgB,QAAQ;EACpB,OAAO,MAAM,QAAQ;GACjB,MAAM;GACN,aAAa;GACb,SAAS;GACZ,CAAC;EACF,MAAM,MAAM,QAAQ;GAChB,MAAM;GACN,aAAa;GACb,SAAS;GACZ,CAAC;EACL;CAED,OAAgB,WAAW;EACvB;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACJ;CAED,MAAa,MAAqB;EAC9B,MAAM,EAAE,UAAU,MAAM,KAAK,MAAM,oBAAoB;EAEvD,MAAMA,OAAiB,CAAC,MAAM;AAC9B,MAAI,MAAM,MAAO,MAAK,KAAK,UAAU;AACrC,MAAI,MAAM,KAAM,MAAK,KAAK,SAAS;AAEnC,QAAM,KAAK,eAAe,KAAK;;;;;;ACnDvC,IAAa,uBAAb,cAA0C,iBAAiB;CACvD,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;;CAM9B,OAAgB,WAAW,CACvB;EACI,aAAa;EACb,SAAS;EACZ,CACJ;CAED,MAAa,MAAqB;AAC9B,QAAM,KAAK,eAAe,CAAC,OAAO,CAAC;;;;;;ACf3C,IAAa,sBAAb,MAAa,4BAA4B,iBAAiB;CACtD,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;;;CAO9B,OAAgB,OAAO;EACnB,QAAQ,KAAK,OAAO;GAChB,MAAM;GACN,UAAU;GACV,aAAa;GACb,SAAS,CAAC,SAAS,OAAO;GAC7B,CAAC;EACF,KAAK,KAAK,OAAO;GACb,MAAM;GACN,UAAU;GACV,aAAa;GAChB,CAAC;EACL;CAED,OAAgB,WAAW,CACvB;EACI,aAAa;EACb,SAAS;EACZ,EACD;EACI,aAAa;EACb,SAAS;EACZ,CACJ;CAED,MAAa,MAAqB;EAC9B,MAAM,EAAE,SAAS,MAAM,KAAK,MAAM,oBAAoB;EAEtD,MAAMC,cAAwB,CAAC,OAAO,KAAK,OAAO;AAClD,MAAI,KAAK,WAAW,WAAW,KAAK,IAAK,aAAY,KAAK,SAAS,KAAK,IAAI;AAE5E,QAAM,KAAK,eAAe,YAAY;;;;;;ACzC9C,IAAa,0BAAb,MAAa,gCAAgC,iBAAiB;CAC1D,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;;;CAO9B,OAAgB,QAAQ;EACpB,OAAO,MAAM,OAAO;GAChB,MAAM;GACN,aAAa;GACb,UAAU;GACb,CAAC;EACF,OAAO,MAAM,OAAO;GAChB,MAAM;GACN,aAAa;GACb,UAAU;GACb,CAAC;EACF,cAAc,MAAM,QAAQ;GACxB,aAAa;GACb,UAAU;GACV,SAAS;GACZ,CAAC;EACL;CAED,OAAgB,WAAW;EACvB;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACJ;CAED,MAAa,MAAqB;EAC9B,MAAM,EAAE,UAAU,MAAM,KAAK,MAAM,wBAAwB;EAE3D,MAAMC,OAAiB,CAAC,UAAU;AAClC,MAAI,MAAM,IAAK,MAAK,KAAK,SAAS,MAAM,IAAI;AAC5C,MAAI,MAAM,IAAK,MAAK,KAAK,SAAS,MAAM,IAAI;AAC5C,MAAI,MAAM,cAAe,MAAK,KAAK,eAAe;AAElD,QAAM,KAAK,eAAe,KAAK;;;;;;ACvDvC,IAAa,yBAAb,MAAa,+BAA+B,iBAAiB;CACzD,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;CAK9B,OAAgB,QAAQ;EACpB,SAAS,MAAM,QAAQ;GACnB,MAAM;GACN,aACI;GACJ,UAAU;GACV,SAAS;GACZ,CAAC;EACF,QAAQ,MAAM,OAAO;GACjB,MAAM;GACN,aACI;GACJ,UAAU;GACb,CAAC;EACF,OAAO,MAAM,OAAO;GAChB,MAAM;GACN,aACI;GACJ,UAAU;GACb,CAAC;EACL;CAED,OAAgB,WAAW;EACvB;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aACI;GACJ,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACJ;CAED,MAAa,MAAqB;EAC9B,MAAM,EAAE,UAAU,MAAM,KAAK,MAAM,uBAAuB;EAE1D,MAAMC,OAAiB,CAAC,SAAS;AACjC,MAAI,MAAM,QAAS,MAAK,KAAK,YAAY;AACzC,MAAI,MAAM,OAAQ,MAAK,KAAK,YAAY,MAAM,OAAO;AACrD,MAAI,MAAM,MAAO,MAAK,KAAK,WAAW,MAAM,MAAM;AAElD,QAAM,KAAK,eAAe,KAAK;;;;;;AC5DvC,IAAa,sBAAb,cAAyC,iBAAiB;CACtD,OAAgB,UAAU;CAE1B,OAAgB,cAAc;;;;;;;;;;;;;;;CAgB9B,MAAa,MAAqB;AAC9B,QAAM,KAAK,eAAe,CAAC,MAAM,CAAC;;;;;;AClB1C,IAAa,0BAAb,MAAa,gCAAgC,iBAAiB;CAC1D,OAAgB,UACZ;CAEJ,OAAgB,cAAc;;;;;CAM9B,OAAgB,QAAQ;EACpB,QAAQ,MAAM,OAAO;GACjB,MAAM;GACN,aAAa;GACb,UAAU;GACb,CAAC;EACF,UAAU,MAAM,OAAO;GACnB,MAAM;GACN,aAAa;GACb,UAAU;GACb,CAAC;EACL;CAED,OAAgB,WAAW;EACvB;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACD;GACI,aAAa;GACb,SAAS;GACZ;EACJ;CAED,MAAa,MAAqB;EAC9B,MAAM,EAAE,UAAU,MAAM,KAAK,MAAM,wBAAwB;EAE3D,MAAMC,OAAiB,CAAC,UAAU;AAClC,MAAI,MAAM,OAAQ,MAAK,KAAK,YAAY,MAAM,OAAO;AACrD,MAAI,MAAM,SAAU,MAAK,KAAK,cAAc,MAAM,SAAS;AAE3D,QAAM,KAAK,eAAe,KAAK;;;;;;ACzCvC,MAAa,WAAW;CACpB,kBAAkB;CAClB,iBAAiB;CACjB,qBAAqB;CACrB,qBAAqB;CACrB,oBAAoB;CACpB,iBAAiB;CACjB,iBAAiB;CACpB"}

package/oclif.config.js

@@ -0,0 +1,13 @@
+export default {
+    description: 'Plugin that add the changeset command to the jpp cli.',
+    commands: {
+        strategy: 'explicit',
+        target: './dist/index.mjs',
+        identifier: 'commands',
+    },
+    topics: {
+        changeset: {
+            description: 'Commands for managing changesets.',
+        },
+    },
+};

package/oclif.manifest.json

@@ -0,0 +1,285 @@
+{
+  "commands": {
+    "changeset:init": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThis command sets up the .changeset folder. It generates a readme and a config file.\nThe config file includes the default options and comments on what these options represent.\nYou should run this command once when you are setting up changesets.\n",
+      "examples": [
+        {
+          "description": "Initialize changesets in your repository.",
+          "command": "<%= config.bin %> <%= command.id %>"
+        }
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:init",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Sets up the .changeset folder."
+    },
+    "changeset:add": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThis is the main command people use to interact with the changesets.\n\nThis command will ask you a series of questions, first about what packages you want to release,\nthen what semver bump type for each package, then it will ask for a summary of the entire changeset.\nThe final step will show the changeset it will generate and confirm that you want to add it.\n\nOnce confirmed, the changeset will be written a Markdown file that contains the summary and YAML\nfront matter which stores the packages that will be released and the semver bump types for them.\n",
+      "examples": [
+        {
+          "description": "Add a new changeset to the project.",
+          "command": "<%= config.bin %> <%= command.id %>"
+        },
+        {
+          "description": "Add an empty changeset without any prompts.",
+          "command": "<%= config.bin %> <%= command.id %> --empty"
+        },
+        {
+          "description": "Add a new changeset and open it in the default editor.",
+          "command": "<%= config.bin %> <%= command.id %> --open"
+        }
+      ],
+      "flags": {
+        "empty": {
+          "char": "e",
+          "description": "Create an empty changeset without prompts.",
+          "name": "empty",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "open": {
+          "char": "o",
+          "description": "Open the changeset in the default editor after creating it.",
+          "name": "open",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:add",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Add a new changeset to the project."
+    },
+    "changeset:version": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThis is one of two commands responsible for releasing packages. The version command takes changesets\nthat have been made and updates versions and dependencies of packages, as well as writing\nchangelogs. It is responsible for all file changes to versions before publishing to npm.\n",
+      "examples": [
+        {
+          "description": "Version packages based on changesets.",
+          "command": "<%= config.bin %> <%= command.id %>"
+        },
+        {
+          "description": "Version packages while ignoring specific packages.",
+          "command": "<%= config.bin %> <%= command.id %> --ignore package-a,package-b"
+        },
+        {
+          "description": "Version packages with snapshot versions.",
+          "command": "<%= config.bin %> <%= command.id %> --snapshot beta"
+        }
+      ],
+      "flags": {
+        "ignore": {
+          "char": "i",
+          "description": "Comma-separated list of packages to ignore when versioning.",
+          "name": "ignore",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "snapshot": {
+          "char": "s",
+          "description": "Create snapshot versions with the given tag.",
+          "name": "snapshot",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:version",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Takes changesets that have been made and updates versions and dependencies of packages, as well as writing changelogs."
+    },
+    "changeset:publish": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThis publishes changes to npm, and creates git tags. This works by going into each package, checking\nif the version it has in its package.json is published on npm, and if it is not, running the npm\npublish. If you are using pnpm as a package manager, this automatically detects it and uses pnpm\npublish instead.\n",
+      "examples": [
+        {
+          "description": "Publish packages to npm and create git tags.",
+          "command": "<%= config.bin %> <%= command.id %>"
+        },
+        {
+          "description": "Publish packages with a one-time password.",
+          "command": "<%= config.bin %> <%= command.id %> --otp 123456"
+        },
+        {
+          "description": "Publish packages under a specific tag.",
+          "command": "<%= config.bin %> <%= command.id %> --tag beta"
+        },
+        {
+          "description": "Publish packages without creating git tags.",
+          "command": "<%= config.bin %> <%= command.id %> --no-git-tag"
+        }
+      ],
+      "flags": {
+        "otp": {
+          "char": "o",
+          "description": "One-time password for publishing to npm.",
+          "name": "otp",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "tag": {
+          "char": "t",
+          "description": "Tag to publish the package under.",
+          "name": "tag",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "no-git-tag": {
+          "description": "Skip creating a git tag after publishing.",
+          "name": "no-git-tag",
+          "required": false,
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:publish",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Publishes changes to npm, and creates git tags."
+    },
+    "changeset:status": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThe status command provides information about the changesets that currently exist. If there are no\nchangesets present, it exits with an error status code.\n",
+      "examples": [
+        {
+          "description": "Get the status of changesets in the project.",
+          "command": "<%= config.bin %> <%= command.id %>"
+        },
+        {
+          "description": "Get a verbose status of changesets, including new versions and links to summaries.",
+          "command": "<%= config.bin %> <%= command.id %> --verbose"
+        },
+        {
+          "description": "Output the status of changesets as a JSON object.",
+          "command": "<%= config.bin %> <%= command.id %> --output status.json"
+        },
+        {
+          "description": "Get the status of changesets since a specific branch or git tag.",
+          "command": "<%= config.bin %> <%= command.id %> --since main"
+        }
+      ],
+      "flags": {
+        "verbose": {
+          "char": "v",
+          "description": "Use if you want to know the new versions, and get a link to the relevant changeset summary.",
+          "name": "verbose",
+          "required": false,
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "output": {
+          "char": "o",
+          "description": "Allows you to write the JSON object of the status output for consumption by other tools, such as CI.",
+          "name": "output",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "since": {
+          "char": "s",
+          "description": "Only display information about changesets since a specific branch or git tag (such as main, or the git hash of latest).",
+          "name": "since",
+          "required": false,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:status",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Provides information about the changesets that currently exist."
+    },
+    "changeset:pre": {
+      "aliases": [],
+      "args": {
+        "action": {
+          "description": "The pre-release action to perform.",
+          "name": "action",
+          "options": [
+            "enter",
+            "exit"
+          ],
+          "required": true
+        },
+        "tag": {
+          "description": "The pre-release tag to use when entering pre-release mode.",
+          "name": "tag",
+          "required": false
+        }
+      },
+      "description": "\nThe pre command enters and exits pre mode. The command does not do any actual versioning, when doing\na pre-release, you should run changeset pre enter next(or a different tag, the tag is what is in\nversions and is the npm dist tag) and then do the normal release process with changeset version and\nchangeset publish.\n",
+      "examples": [
+        {
+          "description": "Enter pre-release mode with the \"next\" tag.",
+          "command": "<%= config.bin %> <%= command.id %> enter next"
+        },
+        {
+          "description": "Exit pre-release mode.",
+          "command": "<%= config.bin %> <%= command.id %> exit"
+        }
+      ],
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:pre",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Enters and exits pre-release mode for packages."
+    },
+    "changeset:tag": {
+      "aliases": [],
+      "args": {},
+      "description": "\nThe tag command creates git tags for the current version of all packages. The tags created are\nequivalent to those created by changeset publish, but the tag command does not publish anything to\nnpm.\n\nThis is helpful in situations where a different tool, such as pnpm publish -r, is used to publish\npackages instead of changeset. For situations where changeset publish is executed, running changeset\ntag is not needed.\n\nThe git tags in monorepos are created in the format pkg-name@version-number and are based on the\ncurrent version number of the package.json for each package. Note that in single-package\nrepositories, the git tag will include v before the version number, for example, v1.0.0. It is\nexpected that changeset version is run before changeset tag, so the package.json versions are\nupdated before the git tags are created.\n",
+      "flags": {},
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "changeset:tag",
+      "pluginAlias": "@jpp-toolkit/plugin-changesets",
+      "pluginName": "@jpp-toolkit/plugin-changesets",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Creates git tags for the current version of all packages."
+    }
+  },
+  "version": "0.0.11"
+}

package/package.json

@@ -0,0 +1,60 @@
+{
+  "name": "@jpp-toolkit/plugin-changesets",
+  "version": "0.0.11",
+  "description": "Plugin that add the changeset command to the jpp cli.",
+  "keywords": [
+    "jpp",
+    "plugin",
+    "changesets"
+  ],
+  "homepage": "https://github.com/jpapini/jpp-toolkit/tree/main/packages/plugin-changesets#readme",
+  "bugs": {
+    "url": "https://github.com/jpapini/jpp-toolkit/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jpapini/jpp-toolkit.git",
+    "directory": "packages/plugin-changesets"
+  },
+  "license": "MIT",
+  "author": "Julien Papini <julien.papini@gmail.com> (https://github.com/jpapini)",
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.mts",
+      "default": "./dist/index.mjs"
+    },
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "src",
+    "oclif.config.js",
+    "oclif.manifest.json"
+  ],
+  "dependencies": {
+    "@changesets/cli": "2.29.8",
+    "@oclif/core": "4.8.0",
+    "execa": "9.6.1",
+    "@jpp-toolkit/core": "0.0.11",
+    "@jpp-toolkit/utils": "0.0.11"
+  },
+  "devDependencies": {
+    "oclif": "4.22.52"
+  },
+  "engines": {
+    "node": "24",
+    "pnpm": "10"
+  },
+  "volta": {
+    "extends": "../../package.json"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit --pretty",
+    "dev": "build-lib --watch",
+    "build": "build-lib"
+  }
+}

package/src/add-changeset-command.ts

@@ -0,0 +1,56 @@
+import { Flags } from '@oclif/core';
+
+import { ChangesetCommand } from './changeset-command';
+
+export class AddChangesetCommand extends ChangesetCommand {
+    static override summary = 'Add a new changeset to the project.';
+
+    static override description = `
+This is the main command people use to interact with the changesets.
+
+This command will ask you a series of questions, first about what packages you want to release,
+then what semver bump type for each package, then it will ask for a summary of the entire changeset.
+The final step will show the changeset it will generate and confirm that you want to add it.
+
+Once confirmed, the changeset will be written a Markdown file that contains the summary and YAML
+front matter which stores the packages that will be released and the semver bump types for them.
+`;
+
+    static override flags = {
+        empty: Flags.boolean({
+            char: 'e',
+            description: 'Create an empty changeset without prompts.',
+            default: false,
+        }),
+        open: Flags.boolean({
+            char: 'o',
+            description: 'Open the changeset in the default editor after creating it.',
+            default: false,
+        }),
+    };
+
+    static override examples = [
+        {
+            description: 'Add a new changeset to the project.',
+            command: '<%= config.bin %> <%= command.id %>',
+        },
+        {
+            description: 'Add an empty changeset without any prompts.',
+            command: '<%= config.bin %> <%= command.id %> --empty',
+        },
+        {
+            description: 'Add a new changeset and open it in the default editor.',
+            command: '<%= config.bin %> <%= command.id %> --open',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        const { flags } = await this.parse(AddChangesetCommand);
+
+        const args: string[] = ['add'];
+        if (flags.empty) args.push('--empty');
+        if (flags.open) args.push('--open');
+
+        await this._execChangeset(args);
+    }
+}

package/src/changeset-command.ts

@@ -0,0 +1,19 @@
+import { createRequire } from 'node:module';
+import path from 'node:path';
+
+import { Command } from '@jpp-toolkit/core';
+import { findProjectRoot } from '@jpp-toolkit/utils';
+import { execa } from 'execa';
+
+const require = createRequire(import.meta.url);
+
+const CHANGESET_BIN = path.resolve(require.resolve('@changesets/cli/package.json'), '../bin.js');
+
+export abstract class ChangesetCommand extends Command {
+    protected async _execChangeset(args: string[] = []): Promise<void> {
+        const cwd = findProjectRoot();
+        const result = await execa(CHANGESET_BIN, args, { cwd, stdio: 'inherit', reject: false });
+
+        if (result.failed) process.exit(1);
+    }
+}

package/src/index.ts

@@ -0,0 +1,17 @@
+import { AddChangesetCommand } from './add-changeset-command';
+import { InitChangesetCommand } from './init-changeset-command';
+import { PreChangesetCommand } from './pre-changeset-command';
+import { PublishChangesetCommand } from './publish-changeset-command';
+import { StatusChangesetCommand } from './status-changeset-command';
+import { TagChangesetCommand } from './tag-changeset-command';
+import { VersionChangesetCommand } from './version-changeset-command';
+
+export const commands = {
+    'changeset:init': InitChangesetCommand,
+    'changeset:add': AddChangesetCommand,
+    'changeset:version': VersionChangesetCommand,
+    'changeset:publish': PublishChangesetCommand,
+    'changeset:status': StatusChangesetCommand,
+    'changeset:pre': PreChangesetCommand,
+    'changeset:tag': TagChangesetCommand,
+};

package/src/init-changeset-command.ts

@@ -0,0 +1,22 @@
+import { ChangesetCommand } from './changeset-command';
+
+export class InitChangesetCommand extends ChangesetCommand {
+    static override summary = 'Sets up the .changeset folder.';
+
+    static override description = `
+This command sets up the .changeset folder. It generates a readme and a config file.
+The config file includes the default options and comments on what these options represent.
+You should run this command once when you are setting up changesets.
+`;
+
+    static override examples = [
+        {
+            description: 'Initialize changesets in your repository.',
+            command: '<%= config.bin %> <%= command.id %>',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        await this._execChangeset(['init']);
+    }
+}

package/src/pre-changeset-command.ts

@@ -0,0 +1,48 @@
+import { Args } from '@oclif/core';
+
+import { ChangesetCommand } from './changeset-command';
+
+export class PreChangesetCommand extends ChangesetCommand {
+    static override summary = 'Enters and exits pre-release mode for packages.';
+
+    static override description = `
+The pre command enters and exits pre mode. The command does not do any actual versioning, when doing
+a pre-release, you should run changeset pre enter next(or a different tag, the tag is what is in
+versions and is the npm dist tag) and then do the normal release process with changeset version and
+changeset publish.
+`;
+
+    static override args = {
+        action: Args.string({
+            name: 'action',
+            required: true,
+            description: 'The pre-release action to perform.',
+            options: ['enter', 'exit'],
+        }),
+        tag: Args.string({
+            name: 'tag',
+            required: false,
+            description: 'The pre-release tag to use when entering pre-release mode.',
+        }),
+    };
+
+    static override examples = [
+        {
+            description: 'Enter pre-release mode with the "next" tag.',
+            command: '<%= config.bin %> <%= command.id %> enter next',
+        },
+        {
+            description: 'Exit pre-release mode.',
+            command: '<%= config.bin %> <%= command.id %> exit',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        const { args } = await this.parse(PreChangesetCommand);
+
+        const commandArgs: string[] = ['pre', args.action];
+        if (args.action === 'enter' && args.tag) commandArgs.push('--tag', args.tag);
+
+        await this._execChangeset(commandArgs);
+    }
+}

package/src/publish-changeset-command.ts

@@ -0,0 +1,62 @@
+import { Flags } from '@oclif/core';
+
+import { ChangesetCommand } from './changeset-command';
+
+export class PublishChangesetCommand extends ChangesetCommand {
+    static override summary = 'Publishes changes to npm, and creates git tags.';
+
+    static override description = `
+This publishes changes to npm, and creates git tags. This works by going into each package, checking
+if the version it has in its package.json is published on npm, and if it is not, running the npm
+publish. If you are using pnpm as a package manager, this automatically detects it and uses pnpm
+publish instead.
+`;
+
+    static override flags = {
+        'otp': Flags.string({
+            char: 'o',
+            description: 'One-time password for publishing to npm.',
+            required: false,
+        }),
+        'tag': Flags.string({
+            char: 't',
+            description: 'Tag to publish the package under.',
+            required: false,
+        }),
+        'no-git-tag': Flags.boolean({
+            description: 'Skip creating a git tag after publishing.',
+            required: false,
+            default: false,
+        }),
+    };
+
+    static override examples = [
+        {
+            description: 'Publish packages to npm and create git tags.',
+            command: '<%= config.bin %> <%= command.id %>',
+        },
+        {
+            description: 'Publish packages with a one-time password.',
+            command: '<%= config.bin %> <%= command.id %> --otp 123456',
+        },
+        {
+            description: 'Publish packages under a specific tag.',
+            command: '<%= config.bin %> <%= command.id %> --tag beta',
+        },
+        {
+            description: 'Publish packages without creating git tags.',
+            command: '<%= config.bin %> <%= command.id %> --no-git-tag',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        const { flags } = await this.parse(PublishChangesetCommand);
+
+        const args: string[] = ['publish'];
+        if (flags.otp) args.push('--otp', flags.otp);
+        if (flags.tag) args.push('--tag', flags.tag);
+        if (flags['no-git-tag']) args.push('--no-git-tag');
+
+        await this._execChangeset(args);
+    }
+}

package/src/status-changeset-command.ts

@@ -0,0 +1,65 @@
+import { Flags } from '@oclif/core';
+
+import { ChangesetCommand } from './changeset-command';
+
+export class StatusChangesetCommand extends ChangesetCommand {
+    static override summary = 'Provides information about the changesets that currently exist.';
+
+    static override description = `
+The status command provides information about the changesets that currently exist. If there are no
+changesets present, it exits with an error status code.
+`;
+
+    static override flags = {
+        verbose: Flags.boolean({
+            char: 'v',
+            description:
+                'Use if you want to know the new versions, and get a link to the relevant changeset summary.',
+            required: false,
+            default: false,
+        }),
+        output: Flags.string({
+            char: 'o',
+            description:
+                'Allows you to write the JSON object of the status output for consumption by other tools, such as CI.',
+            required: false,
+        }),
+        since: Flags.string({
+            char: 's',
+            description:
+                'Only display information about changesets since a specific branch or git tag (such as main, or the git hash of latest).',
+            required: false,
+        }),
+    };
+
+    static override examples = [
+        {
+            description: 'Get the status of changesets in the project.',
+            command: '<%= config.bin %> <%= command.id %>',
+        },
+        {
+            description:
+                'Get a verbose status of changesets, including new versions and links to summaries.',
+            command: '<%= config.bin %> <%= command.id %> --verbose',
+        },
+        {
+            description: 'Output the status of changesets as a JSON object.',
+            command: '<%= config.bin %> <%= command.id %> --output status.json',
+        },
+        {
+            description: 'Get the status of changesets since a specific branch or git tag.',
+            command: '<%= config.bin %> <%= command.id %> --since main',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        const { flags } = await this.parse(StatusChangesetCommand);
+
+        const args: string[] = ['status'];
+        if (flags.verbose) args.push('--verbose');
+        if (flags.output) args.push('--output', flags.output);
+        if (flags.since) args.push('--since', flags.since);
+
+        await this._execChangeset(args);
+    }
+}

package/src/tag-changeset-command.ts

@@ -0,0 +1,25 @@
+import { ChangesetCommand } from './changeset-command';
+
+export class TagChangesetCommand extends ChangesetCommand {
+    static override summary = 'Creates git tags for the current version of all packages.';
+
+    static override description = `
+The tag command creates git tags for the current version of all packages. The tags created are
+equivalent to those created by changeset publish, but the tag command does not publish anything to
+npm.
+
+This is helpful in situations where a different tool, such as pnpm publish -r, is used to publish
+packages instead of changeset. For situations where changeset publish is executed, running changeset
+tag is not needed.
+
+The git tags in monorepos are created in the format pkg-name@version-number and are based on the
+current version number of the package.json for each package. Note that in single-package
+repositories, the git tag will include v before the version number, for example, v1.0.0. It is
+expected that changeset version is run before changeset tag, so the package.json versions are
+updated before the git tags are created.
+`;
+
+    public async run(): Promise<void> {
+        await this._execChangeset(['tag']);
+    }
+}

package/src/version-changeset-command.ts

@@ -0,0 +1,52 @@
+import { Flags } from '@oclif/core';
+
+import { ChangesetCommand } from './changeset-command';
+
+export class VersionChangesetCommand extends ChangesetCommand {
+    static override summary =
+        'Takes changesets that have been made and updates versions and dependencies of packages, as well as writing changelogs.';
+
+    static override description = `
+This is one of two commands responsible for releasing packages. The version command takes changesets
+that have been made and updates versions and dependencies of packages, as well as writing
+changelogs. It is responsible for all file changes to versions before publishing to npm.
+`;
+
+    static override flags = {
+        ignore: Flags.string({
+            char: 'i',
+            description: 'Comma-separated list of packages to ignore when versioning.',
+            required: false,
+        }),
+        snapshot: Flags.string({
+            char: 's',
+            description: 'Create snapshot versions with the given tag.',
+            required: false,
+        }),
+    };
+
+    static override examples = [
+        {
+            description: 'Version packages based on changesets.',
+            command: '<%= config.bin %> <%= command.id %>',
+        },
+        {
+            description: 'Version packages while ignoring specific packages.',
+            command: '<%= config.bin %> <%= command.id %> --ignore package-a,package-b',
+        },
+        {
+            description: 'Version packages with snapshot versions.',
+            command: '<%= config.bin %> <%= command.id %> --snapshot beta',
+        },
+    ];
+
+    public async run(): Promise<void> {
+        const { flags } = await this.parse(VersionChangesetCommand);
+
+        const args: string[] = ['version'];
+        if (flags.ignore) args.push('--ignore', flags.ignore);
+        if (flags.snapshot) args.push('--snapshot', flags.snapshot);
+
+        await this._execChangeset(args);
+    }
+}