chore(140): repoint github URLs at pipefy/ai-toolkit#271
Merged
Conversation
Rewrite every github.com / raw.githubusercontent.com owner-path reference from gbrlcustodio/pipefy-mcp-server to pipefy/ai-toolkit ahead of the repo rename and org transfer (#140), and drop the community-maintained disclaimer now that the repo moves under the Pipefy org. Scope is URL paths only. Distribution names (pipefy-mcp-server, pipefy-cli, pipefy-sdk, pipefy-auth, pipefy-infra) are left untouched: renaming them would break every existing install script. CHANGELOG entries are left as shipped historical records. Staged unmerged: every pipefy/ai-toolkit URL is dead until the org and repo exist, so this must merge in the transfer window, not before.
18 tasks
adriannoes
approved these changes
Jun 2, 2026
Collaborator
There was a problem hiding this comment.
Summary
Reviewed statically on head 2024a70 (URL/docs chore only; no runtime logic). The diff consistently repoints install and docs surfaces from gbrlcustodio/pipefy-mcp-server to pipefy/ai-toolkit, updates DOCS_SETUP_REF, and leaves distribution names and CHANGELOG history alone as scoped. git grep 'gbrlcustodio/pipefy-mcp-server' on the PR branch leaves only the two intentional CHANGELOG.md lines; CI (lint, test, skill frontmatter) is green.
Approve the change set. Merge only in the #140 transfer window — every pipefy/ai-toolkit URL is dead until the org/repo exists, as you already documented.
Also noted
- #260: If release-wheel
.mcp.jsonlands first, dropping this PR’s.mcp.jsonhunk on rebase is fine. .claude-plugin/marketplace.json: Still lists owner profilehttps://github.com/gbrlcustodio(not in this PR’s file list). Optional follow-up tohttps://github.com/pipefywhen you refresh marketplace metadata after transfer.
gbrlcustodio
added a commit
that referenced
this pull request
Jun 2, 2026
…s at pipefy/ai-toolkit #271 (org rename) landed in main while this branch carried the release-wheel work. Resolved .mcp.json and commands/install.md to keep the wheel-URL and install.sh-delegation behavior from this branch, and repointed the new paste-into-config wheel URLs in packages/mcp/README.md (added here, so they auto-merged still on the old org) to pipefy/ai-toolkit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Repoint every
github.com/raw.githubusercontent.comowner-path reference fromgbrlcustodio/pipefy-mcp-servertopipefy/ai-toolkit, ahead of the repo rename and org transfer tracked in #140. Also drops the "community-maintained / not an official Pipefy product" disclaimer from the README, since the repo moves under the Pipefy org.Do not merge before the transfer. Every
pipefy/ai-toolkitURL is dead until the org and repo exist. Merging early breaksinstall.sh, the README CI badge, and the bootstrapcurl. Sequence: approve now, transfer + re-add secrets / branch protection / webhooks, then merge in the same window.Scope
URL paths only. Files touched:
install.sh(theREPO=constant),README.md(badge, release link, install examples, issues link, disclaimer removal),packages/mcp/README.md,packages/cli/README.md,commands/install.md(bootstrap curl),docs/MIGRATION.md,skills/README.md,RELEASE.md,packages/mcp/src/pipefy_mcp/_docs.py,.claude-plugin/plugin.json(homepage/repository),.mcp.json.Deliberately left alone
pipefy-mcp-server,pipefy-cli,pipefy-sdk,pipefy-auth,pipefy-infra). These are consumer-facing PyPI/install identifiers; renaming them breaks every install script. Tracked as an open question on Rename toai-toolkitand transfer to the Pipefy GitHub org #140, out of scope here.CHANGELOG.md(2 entries). Historical release records; not rewritten.# pipefy-labsumbrella heading. Rename toai-toolkitand transfer to the Pipefy GitHub org #140 lists this as an undecided naming question (keep / rename / drop), so it stays until that's settled.Interaction with #260
#260 (wheel-URL install) is unmerged. It rewrites
.mcp.jsonto release-wheel URLs and adds arelease.ymlstep that regenerates those URLs fromGITHUB_REPOSITORYon every release. If #260 lands first,.mcp.jsonself-heals on the next release and this PR's.mcp.jsonhunk becomes a moot conflict to drop at rebase. This PR is correct against currentmain, where.mcp.jsonis still the@latestgit form and does not self-heal.Not covered (needs a runbook, not a PR)
The operational transfer mechanics: re-add Actions secrets (release signing / future PyPI OIDC), re-apply branch protection, re-verify webhooks. See #140's "Transfer mechanics" checklist.
Verification
grep -rn "gbrlcustodio/pipefy-mcp-server"returns only the two intentionalCHANGELOG.mdentries.pyproject.toml[project].namechanged..mcp.jsonand.claude-plugin/plugin.jsonparse as JSON;pipefy_mcp._docsimports.curl -fsSL https://raw.githubusercontent.com/pipefy/ai-toolkit/main/install.sh | sh -s -- --yes --no-skills --client none --dry-runshould printResolved tag: vX.Y.Z.