sqitch-bundle(3pm)

💖 NAME 💖

sqitch-bundle — bundle a Sqitch project for distribution, bestie. That's it, that's the whole vibe. 🎀

---

✨ SYNOPSIS ✨

sqitch bundle [options]
sqitch bundle --dest-dir widgets-1.0.0
sqitch bundle --all
sqitch bundle pg mysql

---

🦋 DESCRIPTION 🦋

Okay so this command bundles up a sqitch project for distribution. At its simplest, it copies the project configuration file, plan files, and all the change scripts into a directory. Then you can package that directory up for distribution — as a tarball, an RPM, whatever. Slay. ✨

By default, the bundle command bundles the plan and scripts for the default plan and top directory, as defined by the core configuration and command-line options. Wanna go bigger? Pass the --all option and it will iterate over all known plans and top directories (as specified for engines and targets) and bundle them all. This works well for creating a single bundle with all plans and scripts. Iconic. 👑

To pick which plans and top directories to bundle, pass the target, engine, or plan file names as arguments. Check "Examples" for the receipts.

• Engine names
• Target names
• Plan file names

The bundle command also lets you limit bundled changes to a subset of the ones in a plan. Bundling a single plan? Use the --from and/or --to options to do the limiting. Using multiple plans? Specify the changes after each target argument. Either way, the changes can be specified in any way documented on sqitchchanges. See "Examples" for examples.

---

💅 OPTIONS 💅

• --dest-dir, --dir — the name of the directory in which to bundle the project. The configuration file gets created in this directory, and all the top, deploy, revert, and verify directories will be created relative to it. Defaults to bundle.
• --from — the change from which to start bundling. Need to bundle up only a subset of a plan? Specify a change (using a supported change specification) from which to start the bundling via this option. This option is probably only useful when bundling a single plan.
• --to — the change to which to end bundling. Need to bundle up only a subset of a plan? Specify a change (using a supported change specification) that should be the last change included in the bundle. This option is probably only useful when bundling a single plan.
• -a, --all — bundle all the project plans and their associated scripts. Cannot be mixed with target, engine, or plan file name arguments — doing so will result in an error. Useful for multi-plan projects that should have all the plans bundled together. Overrides the value of the bundle.all configuration; use --no-all to override a true bundle.all configuration.
• --plan-file, -f — path to the deployment plan file. Overrides target, engine, and core configuration values. Defaults to $top_dir/sqitch.plan.

ngl, that "cannot be mixed" thing is not a suggestion, bestie. The command will literally error out. 💀

---

🌸 CONFIGURATION VARIABLES 🌸

• bundle.dest_dir — the name of the directory in which to bundle the project.

---

🍓 EXAMPLES 🍓

Bundle a Sqitch project with the default plan and scripts into bundle:

sqitch bundle

Bundle a Sqitch project with all plans and scripts into bundle:

sqitch bundle --all

Bundle a Sqitch project into BUILDROOT/MyProj:

sqitch bundle --dest-dir BUILDROOT/MyProj

Bundle a project including changes adduser through @v1.0:

sqitch bundle --from adduser --to @v1.0

Bundle the pg engine plans with changes adduser through @v1.0, and the sqlite engine with changes from the start of the plan up to widgets:

sqitch bundle pg adduser @v1.0 sqlite @ROOT wigets

Bundle just the files necessary to execute the plan for the pg engine:

sqitch bundle pg

Bundle the files necessary for two plan files:

sqitch bundle sqlite/sqitch.plan mysql/sqitch.plan

---

🧚 SQITCH 🧚

Part of the sqitch suite. 🫶

---

perl v5.40.1 · 2026-07-26 — that's the version and date this lil page came from, mwah. 💜 Thanks for reading all the way to the bottom, you're the main character fr fr. ✨🦋