* Remove beta release workflow and simplify stable release
Beta release is no longer used. Remove the workflow and simplify the
stable release to only support direct releases with a required version
input.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix npm OIDC: restore registry-url, clear NODE_AUTH_TOKEN, use Node 22
Previous fix removed registry-url entirely, causing ENEEDAUTH (no auth
at all). The correct approach: keep registry-url so npm knows the
endpoint, but clear NODE_AUTH_TOKEN at publish time so npm falls back
to OIDC. Also bump to Node 22 which ships with npm OIDC support.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix npm OIDC: use Node 24 for publish, unset bogus NODE_AUTH_TOKEN
Root cause: setup-packages resets Node to v20 (from .nvmrc), wiping
the npm upgrade. Node 20 ships with npm 10.x which has no OIDC
support. Fix: switch to Node 24 (ships with npm 11.5.1+) right before
publish, and unset the bogus NODE_AUTH_TOKEN that setup-node creates.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Remove beta release workflow and simplify stable release
Beta release is no longer used. Remove the workflow and simplify the
stable release to only support direct releases with a required version
input.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix npm OIDC: restore registry-url, clear NODE_AUTH_TOKEN, use Node 22
Previous fix removed registry-url entirely, causing ENEEDAUTH (no auth
at all). The correct approach: keep registry-url so npm knows the
endpoint, but clear NODE_AUTH_TOKEN at publish time so npm falls back
to OIDC. Also bump to Node 22 which ships with npm OIDC support.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Remove beta release workflow and simplify stable release
Beta release is no longer used. Remove the workflow and simplify the
stable release to only support direct releases with a required version
input.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Fix npm publish by removing setup-node registry config that blocks OIDC
setup-node with registry-url sets NODE_AUTH_TOKEN to the GitHub token,
which npm uses instead of its OIDC flow, causing auth failures. Remove
registry-url/always-auth and switch beta workflow to OIDC too.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Add a new smoke-api test suite that proves the CLI can complete real LLM
round-trips against the Anthropic API. Tests cover headless mode,
serve mode, and all-tools execution. Runs sequentially to avoid rate
limits, skips gracefully when API keys are missing (fork PRs), and
is wired into CI as a required check with allowed-skips.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Node 20 ships with npm 10.x which doesn't support OIDC-based publish
authentication. Trusted publishing requires npm >= 11.5.1.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add --provenance flag to npm publish so it uses the GitHub OIDC token
exchange instead of the expired NODE_AUTH_TOKEN for authentication.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Download the suggestions CLI binary from GitHub Releases during
blueprint build so it's available at /usr/local/bin/suggestions
without runtime downloads.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The @vscode/ripgrep package requires authentication when downloading from
GitHub's API to avoid rate limiting (403 errors). This was causing flaky
test failures in vscode-e2e-tests.
Added github_token input to the run-vscode-e2e-test action and pass
CI_GITHUB_TOKEN to the e2e tests in pr-checks.yaml.
Generated with Continue
Co-Authored-By: Continue <noreply@continue.dev>
Co-authored-by: isabensusan <isabensusan@gmail.com>
The cn-staging blueprint was not being rebuilt when CLI changes were
released, causing staging devboxes to run old code. This updates the
stable release workflow to publish both cn and cn-staging blueprints.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- continue-agents.yml: Use env var for agent name in Create Check Run step
(prevents JS template literal breakage with backticks in filenames)
- run-continue-agent.yml: Use jq to construct JSON body instead of
string interpolation (prevents JSON syntax errors when prompt contains
quotes, newlines, backslashes, or other special characters)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The Write job summary step had the same issue - backticks in the agent
output were being interpreted as bash command substitution, causing
'syntax error near unexpected token' failures.
Use environment variables and printf instead of echo to safely handle
all special characters in the output.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The "Update Check Run" step was interpolating step outputs directly into
JavaScript template literals, which breaks when the agent output contains
backticks, template literal interpolation sequences, or other special
characters that interfere with JS string parsing.
This caused failures like "SyntaxError: Unexpected identifier 'mobile'" when
the agent output contained multi-line text with certain keywords.
Fix by passing outputs as environment variables and accessing them via
process.env, which safely handles all string content without parsing issues.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
A reusable GitHub Actions workflow that discovers and runs Continue agent
files from `.continue/agents/` on pull requests.
Usage:
```yaml
name: Run Continue Agents
on:
pull_request:
types: [opened, synchronize]
jobs:
agents:
uses: continuedev/continue/.github/workflows/continue-agents.yml@main
secrets:
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
```
Features:
- Discovers all .md agent files in .continue/agents/
- Runs each agent in parallel via matrix strategy
- Shows agent output in job logs, job summary, and check runs
- Properly fails jobs when agents fail
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add runloop-blueprint-staging-template.json with name "cn-staging"
- Update upload workflow to use matrix strategy for both blueprints
This enables testing blueprint changes in staging before production.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add `npm cache clean --force` at the end of the base blueprint setup
to prevent "idealTree already exists" errors in child blueprints.
The npm global install leaves cache state that can cause issues when
child blueprints run their own npm install commands.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add google-labs-jules[bot] to the CLA allowlist to allow automated commits from this bot to pass CLA checks without requiring manual signature.
This bot is used for automated code improvements and should be treated similarly to other approved bots like continue[bot] and dependabot[bot].
Generated with [Continue](https://continue.dev)
Co-Authored-By: Continue <noreply@continue.dev>
Co-authored-by: nate <nate@continue.dev>
