Skip to content

feature/Workspace-docs-paths · L-260914-d5ba1e — release play moved to docs/workspace #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lchoquel merged 1 commit into from
Sep 24, 2026
Merged

feature/Workspace-docs-paths · L-260914-d5ba1e — release play moved to docs/workspace #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/skills/release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ description: >

# Releasing pipelex-sdk-python

The procedure is the workspace release play, [`docs/releasing.md`](../../../../docs/releasing.md) at the workspace root — read it first, then run it with what follows. The repo key is `pipelex-sdk-python`, the base is `dev`, and the pull request targets `main`: `guard-branches.yml`'s `gate-main` refuses any head branch but `release/vX.Y.Z` into `main`, so there is no other way in. The release worktree is `_pipelex-sdk-python--release`, made with `wt add pipelex-sdk-python release --branch release/vX.Y.Z`. The repo declares neither `.worktree.toml` nor `.worktreeinclude`, so `wt` resolves the base from `origin/dev` and provisions with the Makefile's `install` target, which is what creates the `.venv` every gate below runs out of. The distribution is `pipelex-sdk` and the import package is `pipelex_sdk`; the version number is the distribution's.
The procedure is the workspace release play, [`docs/workspace/releasing.md`](../../../../docs/workspace/releasing.md) at the workspace root — read it first, then run it with what follows. The repo key is `pipelex-sdk-python`, the base is `dev`, and the pull request targets `main`: `guard-branches.yml`'s `gate-main` refuses any head branch but `release/vX.Y.Z` into `main`, so there is no other way in. The release worktree is `_pipelex-sdk-python--release`, made with `wt add pipelex-sdk-python release --branch release/vX.Y.Z`. The repo declares neither `.worktree.toml` nor `.worktreeinclude`, so `wt` resolves the base from `origin/dev` and provisions with the Makefile's `install` target, which is what creates the `.venv` every gate below runs out of. The distribution is `pipelex-sdk` and the import package is `pipelex_sdk`; the version number is the distribution's.

## What ships

Expand Down
Loading