Data Prep Kit Release Management Skill
You are guiding the user through the data-prep-kit release process. This is a monorepo with three independently versioned packages:
| Package |
Version var |
Suffix var |
| data-processing-lib |
DPK_NEXT_RELEASE |
DPK_VERSION_SUFFIX |
| data-connector-lib |
DPK_CONNECTOR_NEXT_RELEASE |
DPK_CONNECTOR_SUFFIX |
| transforms |
TRANSFORM_NEXT_RELEASE |
TRANSFORM_VERSION_SUFFIX |
All versions live in .make.versions (single source of truth). After editing versions, make set-versions propagates them to all pyproject.toml files.
NOTE — connector is independent: data-connector-lib is versioned on its own track (e.g. 0.2.x) and is not always part of a release, so the root make set-versions deliberately does not recurse into it. When the connector IS being released alongside the other packages (as it is in some releases), you must propagate its version separately: make -C data-connector-lib set-versions. After running it, verify data-connector-lib/pyproject.toml matches DPK_CONNECTOR_NEXT_RELEASE + DPK_CONNECTOR_SUFFIX. If the connector is not part of this release, leave its version untouched.
When invoked, present a menu
Ask the user which release step to perform:
- Step 0: Dev1 Regression Build — Create a
x.x.x.dev1 branch for regression testing
- Step 1: Pending Release — Create a
pending-release/x.x.x branch with clean versions
- Step 2: Create Release — Guide creation of the release branch and tag on GitHub
- Step 3: Post-Release Dev Setup — Bump versions and restore
.dev0 suffix for new development
- Full Release Walkthrough — Walk through all steps end-to-end
- Release Status Check — Analyze current repo state and determine where we are in the release process
Implementation details for each step
Step 0: Dev1 Regression Build
Purpose: Create a dev1 pre-release wheel for regression testing before the final release.
- Confirm the user is on the
dev branch and it is up to date:git checkout dev
git pull
- Read
.make.versions to determine the current *_NEXT_RELEASE values. Confirm the target version with the user (e.g., 1.1.8).
- Create the dev1 branch:
git checkout -b x.x.x.dev1
- Edit
.make.versions — set all relevant suffixes to .dev1:
DPK_VERSION_SUFFIX=.dev1
DPK_CONNECTOR_SUFFIX=.dev1
TRANSFORM_VERSION_SUFFIX=.dev1
- Run
make set-versions to propagate version changes to all pyproject.toml files. If the connector is part of this release, also run make -C data-connector-lib set-versions (the root recursion skips it by design).
- Verify versions propagated correctly by reading the pyproject.toml files for each package — including
data-connector-lib/pyproject.toml if the connector is being released.
- Stage, commit, and push:
git add .
git commit -s -m "adding dev1 release for regression testing"
git push --set-upstream origin x.x.x.dev1
- Create a PR against the
dev branch using gh pr create.
- Inform the user of next steps:
Step 1: Pending Release
Purpose: Remove dev suffixes and prepare the final release version.
- Confirm the user is on the
dev branch and it is up to date:git checkout dev
git pull
- Read
.make.versions to determine the current version numbers. Confirm the target release version with the user.
- Create the pending-release branch:
git checkout -b pending-release/x.x.x
- Edit
.make.versions — clear all suffixes for the components being released:
DPK_VERSION_SUFFIX=
DPK_CONNECTOR_SUFFIX=
TRANSFORM_VERSION_SUFFIX=
- Run
make set-versions to propagate. If the connector is part of this release, also run make -C data-connector-lib set-versions (the root recursion skips it by design).
- Verify versions propagated correctly, including
data-connector-lib/pyproject.toml if the connector is being released.
- Check
release-notes.md for an entry for this version. If missing, prompt the user to provide release notes. Help draft them by:
- Running
git log to find commits since the last release tag
- Categorizing changes into Transforms, General, and other sections
- Following the existing format in
release-notes.md (numbered lists with descriptions)
- Stage, commit, and push:
git add .
git commit -s -m "preparing for a new release"
git push --set-upstream origin pending-release/x.x.x
- Create a PR against the
dev branch using gh pr create.
- Inform the user of next steps:
Step 2: Create Release
Purpose: Create the release branch and tag on GitHub.
This step involves browser-based actions on GitHub. Guide the user through:
- Verify the pending-release PR has been merged and wheels have been published.
- Instruct the user to create a new branch
releases/vx.x.x from dev on GitHub:
- Go to the repository on GitHub
- Click the branch dropdown
- Type
releases/vx.x.x and create from dev
- Instruct the user to create a new release on GitHub:
- Go to Releases > "Draft a new release"
- Create a new tag
vx.x.x targeting the releases/vx.x.x branch
- Title:
vx.x.x
- Copy release notes from
release-notes.md into the release description
- Publish the release
- Alternatively, if
gh CLI is available, offer to automate:gh api repos/{owner}/{repo}/git/refs -f ref="refs/heads/releases/vx.x.x" -f sha="$(git rev-parse dev)"
gh release create vx.x.x --target releases/vx.x.x --title "vx.x.x" --notes-file release-notes-excerpt.md
- Confirm the release was created successfully.
Step 3: Post-Release Dev Setup
Purpose: Bump version numbers and restore dev suffix for ongoing development.
- Confirm the user is on the
dev branch and it is up to date:git checkout dev
git pull
- Read
.make.versions to get current version numbers.
- Ask the user which version component to bump (minor or patch) for each package, or suggest the default (patch bump).
- Create the post-release branch using today's date:
git checkout -b post-YYYY-MM-DD
- Edit
.make.versions:
- Increment the appropriate version component for each
*_NEXT_RELEASE
- Set all suffixes to
.dev0:
DPK_VERSION_SUFFIX=.dev0
DPK_CONNECTOR_SUFFIX=.dev0
TRANSFORM_VERSION_SUFFIX=.dev0
- Run
make set-versions to propagate. If the connector was part of the release, also run make -C data-connector-lib set-versions (the root recursion skips it by design).
- Verify versions propagated correctly, including
data-connector-lib/pyproject.toml if the connector was released.
- Stage, commit, and push:
git add .
git commit -s -m "preparing for a new release"
git push --set-upstream origin post-YYYY-MM-DD
- Create a PR against the
dev branch using gh pr create.
Full Release Walkthrough
Walk through Steps 0-3 sequentially, pausing after each step for user confirmation before proceeding. Track progress and report status at each transition.
Release Status Check
Analyze the current state of the repository to determine where in the release process we are:
- Read
.make.versions and report current versions and suffixes.
- Check the current branch name for clues (
dev, x.x.x.dev1, pending-release/*, post-*).
- Check for recent release tags:
git tag --sort=-creatordate | head -5
- Check for open PRs related to releases:
gh pr list --search "pending-release OR dev1 OR post-"
- Check
release-notes.md for the latest documented version.
- Report:
- Current version state (dev, dev1, release-ready, or post-release)
- What the next step should be
- Any issues found (e.g., mismatched suffixes, missing release notes)
Safety guardrails
- Always confirm with the user before making any edits to
.make.versions or release-notes.md.
- Always show a diff preview of version changes before committing.
- Never run
publish-dist automatically — only instruct the user to do it (from the component folders) after PR merge.
- Never force-push or modify release branches/tags.
- Verify branch state (clean working tree, correct base branch) before creating new branches.
- When creating commits, always use the
-s flag (signed-off-by) as required by the project.
Output format
For each step, produce:
- A clear header indicating the current step
- Pre-flight checks (branch state, version state)
- Actions taken with their results
- Next steps the user needs to complete manually
- A status summary (e.g., "Step 1 complete — pending-release/1.1.8 branch created and PR opened")
1---2name: release3description: Guide and automate release management for data-prep-kit. Covers dev1 regression builds, pending-release branches, release creation, and post-release dev setup. Trigger on "release", "cut a release", "prepare release", "release management", "publish release".4user_invocable: true5metadata:6 source: https://skillmd.com/skills/data-prep-kit/release7---89# Data Prep Kit Release Management Skill1011You are guiding the user through the **data-prep-kit** release process. This is a monorepo with three independently versioned packages:1213| Package | Version var | Suffix var |14|---|---|---|15| data-processing-lib | `DPK_NEXT_RELEASE` | `DPK_VERSION_SUFFIX` |16| data-connector-lib | `DPK_CONNECTOR_NEXT_RELEASE` | `DPK_CONNECTOR_SUFFIX` |17| transforms | `TRANSFORM_NEXT_RELEASE` | `TRANSFORM_VERSION_SUFFIX` |1819All versions live in `.make.versions` (single source of truth). After editing versions, `make set-versions` propagates them to all `pyproject.toml` files.2021> **NOTE — connector is independent:** `data-connector-lib` is versioned on its own track (e.g. `0.2.x`) and is **not** always part of a release, so the root `make set-versions` deliberately does **not** recurse into it. When the connector IS being released alongside the other packages (as it is in some releases), you must propagate its version separately: `make -C data-connector-lib set-versions`. After running it, verify `data-connector-lib/pyproject.toml` matches `DPK_CONNECTOR_NEXT_RELEASE` + `DPK_CONNECTOR_SUFFIX`. If the connector is not part of this release, leave its version untouched.2223## When invoked, present a menu2425Ask the user which release step to perform:26271. **Step 0: Dev1 Regression Build** — Create a `x.x.x.dev1` branch for regression testing282. **Step 1: Pending Release** — Create a `pending-release/x.x.x` branch with clean versions293. **Step 2: Create Release** — Guide creation of the release branch and tag on GitHub304. **Step 3: Post-Release Dev Setup** — Bump versions and restore `.dev0` suffix for new development315. **Full Release Walkthrough** — Walk through all steps end-to-end326. **Release Status Check** — Analyze current repo state and determine where we are in the release process3334---3536## Implementation details for each step3738### Step 0: Dev1 Regression Build3940**Purpose:** Create a dev1 pre-release wheel for regression testing before the final release.41421. Confirm the user is on the `dev` branch and it is up to date:43 ```44 git checkout dev45 git pull46 ```472. Read `.make.versions` to determine the current `*_NEXT_RELEASE` values. Confirm the target version with the user (e.g., `1.1.8`).483. Create the dev1 branch:49 ```50 git checkout -b x.x.x.dev151 ```524. Edit `.make.versions` — set all relevant suffixes to `.dev1`:53 - `DPK_VERSION_SUFFIX=.dev1`54 - `DPK_CONNECTOR_SUFFIX=.dev1`55 - `TRANSFORM_VERSION_SUFFIX=.dev1`565. Run `make set-versions` to propagate version changes to all pyproject.toml files. **If the connector is part of this release**, also run `make -C data-connector-lib set-versions` (the root recursion skips it by design).576. Verify versions propagated correctly by reading the pyproject.toml files for each package — including `data-connector-lib/pyproject.toml` if the connector is being released.587. Stage, commit, and push:59 ```60 git add .61 git commit -s -m "adding dev1 release for regression testing"62 git push --set-upstream origin x.x.x.dev163 ```648. Create a PR against the `dev` branch using `gh pr create`.659. Inform the user of next steps:66 - Review and merge the PR67 - After merge, build and publish wheels for `data-processing-lib` and `transforms`. These targets live in the component Makefiles, not the repo root — run them from each component folder:68 ```69 make -C data-processing-lib build-pkg-dist publish-dist70 make -C transforms build-pkg-dist publish-dist71 ```72 - Test notebooks and confirm success before proceeding to Step 17374### Step 1: Pending Release7576**Purpose:** Remove dev suffixes and prepare the final release version.77781. Confirm the user is on the `dev` branch and it is up to date:79 ```80 git checkout dev81 git pull82 ```832. Read `.make.versions` to determine the current version numbers. Confirm the target release version with the user.843. Create the pending-release branch:85 ```86 git checkout -b pending-release/x.x.x87 ```884. Edit `.make.versions` — clear all suffixes for the components being released:89 - `DPK_VERSION_SUFFIX=`90 - `DPK_CONNECTOR_SUFFIX=`91 - `TRANSFORM_VERSION_SUFFIX=`925. Run `make set-versions` to propagate. **If the connector is part of this release**, also run `make -C data-connector-lib set-versions` (the root recursion skips it by design).936. Verify versions propagated correctly, including `data-connector-lib/pyproject.toml` if the connector is being released.947. Check `release-notes.md` for an entry for this version. If missing, prompt the user to provide release notes. Help draft them by:95 - Running `git log` to find commits since the last release tag96 - Categorizing changes into Transforms, General, and other sections97 - Following the existing format in `release-notes.md` (numbered lists with descriptions)988. Stage, commit, and push:99 ```100 git add .101 git commit -s -m "preparing for a new release"102 git push --set-upstream origin pending-release/x.x.x103 ```1049. Create a PR against the `dev` branch using `gh pr create`.10510. Inform the user of next steps:106 - Review and merge the PR107 - After merge, build and publish wheels for `data-processing-lib` and `transforms`. These targets live in the component Makefiles, not the repo root — run them from each component folder:108 ```109 make -C data-processing-lib build-pkg-dist publish-dist110 make -C transforms build-pkg-dist publish-dist111 ```112 - Proceed to Step 2 to create the actual release113114### Step 2: Create Release115116**Purpose:** Create the release branch and tag on GitHub.117118This step involves browser-based actions on GitHub. Guide the user through:1191201. Verify the pending-release PR has been merged and wheels have been published.1212. Instruct the user to create a new branch `releases/vx.x.x` from `dev` on GitHub:122 - Go to the repository on GitHub123 - Click the branch dropdown124 - Type `releases/vx.x.x` and create from `dev`1253. Instruct the user to create a new release on GitHub:126 - Go to Releases > "Draft a new release"127 - Create a new tag `vx.x.x` targeting the `releases/vx.x.x` branch128 - Title: `vx.x.x`129 - Copy release notes from `release-notes.md` into the release description130 - Publish the release1314. Alternatively, if `gh` CLI is available, offer to automate:132 ```133 gh api repos/{owner}/{repo}/git/refs -f ref="refs/heads/releases/vx.x.x" -f sha="$(git rev-parse dev)"134 gh release create vx.x.x --target releases/vx.x.x --title "vx.x.x" --notes-file release-notes-excerpt.md135 ```1365. Confirm the release was created successfully.137138### Step 3: Post-Release Dev Setup139140**Purpose:** Bump version numbers and restore dev suffix for ongoing development.1411421. Confirm the user is on the `dev` branch and it is up to date:143 ```144 git checkout dev145 git pull146 ```1472. Read `.make.versions` to get current version numbers.1483. Ask the user which version component to bump (minor or patch) for each package, or suggest the default (patch bump).1494. Create the post-release branch using today's date:150 ```151 git checkout -b post-YYYY-MM-DD152 ```1535. Edit `.make.versions`:154 - Increment the appropriate version component for each `*_NEXT_RELEASE`155 - Set all suffixes to `.dev0`:156 - `DPK_VERSION_SUFFIX=.dev0`157 - `DPK_CONNECTOR_SUFFIX=.dev0`158 - `TRANSFORM_VERSION_SUFFIX=.dev0`1596. Run `make set-versions` to propagate. **If the connector was part of the release**, also run `make -C data-connector-lib set-versions` (the root recursion skips it by design).1607. Verify versions propagated correctly, including `data-connector-lib/pyproject.toml` if the connector was released.1618. Stage, commit, and push:162 ```163 git add .164 git commit -s -m "preparing for a new release"165 git push --set-upstream origin post-YYYY-MM-DD166 ```1679. Create a PR against the `dev` branch using `gh pr create`.168169### Full Release Walkthrough170171Walk through Steps 0-3 sequentially, pausing after each step for user confirmation before proceeding. Track progress and report status at each transition.172173### Release Status Check174175Analyze the current state of the repository to determine where in the release process we are:1761771. Read `.make.versions` and report current versions and suffixes.1782. Check the current branch name for clues (`dev`, `x.x.x.dev1`, `pending-release/*`, `post-*`).1793. Check for recent release tags: `git tag --sort=-creatordate | head -5`1804. Check for open PRs related to releases: `gh pr list --search "pending-release OR dev1 OR post-"`1815. Check `release-notes.md` for the latest documented version.1826. Report:183 - Current version state (dev, dev1, release-ready, or post-release)184 - What the next step should be185 - Any issues found (e.g., mismatched suffixes, missing release notes)186187---188189## Safety guardrails190191- **Always confirm with the user** before making any edits to `.make.versions` or `release-notes.md`.192- **Always show a diff preview** of version changes before committing.193- **Never run `publish-dist`** automatically — only instruct the user to do it (from the component folders) after PR merge.194- **Never force-push** or modify release branches/tags.195- **Verify branch state** (clean working tree, correct base branch) before creating new branches.196- When creating commits, always use the `-s` flag (signed-off-by) as required by the project.197198## Output format199200For each step, produce:201- A clear header indicating the current step202- Pre-flight checks (branch state, version state)203- Actions taken with their results204- Next steps the user needs to complete manually205- A status summary (e.g., "Step 1 complete — pending-release/1.1.8 branch created and PR opened")