Skip to content

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.

ci(release-please): use a PAT so releases trigger the publish workflows (#1920)

Tejas Chopra807e5e3e6a1b
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
index 99dce459e..ce458bfd8 100644
--- a/.github/workflows/release-please.yml
+++ b/.github/workflows/release-please.yml
@@ -44,6 +44,14 @@ jobs:
steps:
- uses: googleapis/release-please-action@v5
with:
- token: ${{ secrets.GITHUB_TOKEN }}
+ # PAT (not GITHUB_TOKEN): a release/tag created by GITHUB_TOKEN does
+ # NOT emit events that trigger other workflows, so release.yml
+ # (PyPI/npm) and docker.yml — which fire on `release: published` —
+ # never ran, and releases had to be cut by hand. A PAT is treated as a
+ # real user, so the release it creates DOES trigger those publishes; it
+ # also lets the bot tag past branch/tag protection. Falls back to
+ # GITHUB_TOKEN when the secret is unset (the release PR still opens; it
+ # just won't trigger the downstream publishes).
+ token: ${{ secrets.RELEASE_PLEASE_TOKEN || secrets.GITHUB_TOKEN }}
config-file: .release-please-config.json
manifest-file: .release-please-manifest.json