Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
18b8512
Scope provider profiles by custom storage path
FullstackSensei Nov 2, 2026
698f4df
Fix provider scope test context types
FullstackSensei Nov 2, 2026
4bf8c48
Merge pull request #1 from FullstackSensei/workspace-provider-isolation
FullstackSensei Nov 2, 2026
ee5703c
Ref #2303: Use bracket access in provider tests
FullstackSensei Nov 2, 2026
e4a2fe1
Merge pull request #2 from FullstackSensei/workspace-provider-isolation
FullstackSensei Nov 2, 2026
2057064
Fix invalid custom storage setting fallback
FullstackSensei Nov 2, 2026
c778270
Merge pull request #3 from FullstackSensei/workspace-provider-isolation
FullstackSensei Nov 2, 2026
f48943c
Merge branch 'Zoo-Code-Org:main' into main
FullstackSensei Nov 6, 2026
b1a59cf
Merge branch 'Zoo-Code-Org:main' into workspace-provider-isolation
FullstackSensei Nov 6, 2026
7904704
Preserve task context and add automatic management opt-out
FullstackSensei Nov 6, 2026
07c2417
test(webview): disable transitions in welcome visual tests
FullstackSensei Nov 6, 2026
2eacffa
added translations
FullstackSensei Nov 6, 2026
4ea48f8
Merge pull request #5 from FullstackSensei/workspace-provider-isolation
FullstackSensei Nov 6, 2026
e5eb703
update changelog
FullstackSensei Nov 6, 2026
fbd1593
ci(release): attach VSIX to GitHub Releases without marketplace publi…
FullstackSensei Nov 6, 2026
0efd2bf
Merge pull request #6 from FullstackSensei/release-3.94.1
FullstackSensei Nov 6, 2026
edd424a
bump version in package.json
FullstackSensei Nov 6, 2026
8503483
bump version in package.json
FullstackSensei Nov 6, 2026
ab80a4e
Merge pull request #7 from FullstackSensei/release-3.94.1
FullstackSensei Nov 6, 2026
e8f9472
add version changes in changelog
FullstackSensei Nov 6, 2026
d32f56e
Merge pull request #8 from FullstackSensei/release-3.94.1
FullstackSensei Nov 6, 2026
d84addb
fix changelog header
FullstackSensei Nov 6, 2026
4161974
Merge pull request #9 from FullstackSensei/release-3.94.1
FullstackSensei Nov 6, 2026
95c1861
fix changelog formatting
FullstackSensei Nov 6, 2026
b8e3348
Merge pull request #10 from FullstackSensei/release-3.94.1
FullstackSensei Nov 6, 2026
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
11 changes: 5 additions & 6 deletions .github/workflows/release-kickoff.yml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
name: Weekly release kickoff

# Kicks off the weekly Zoo Code release. The message pings one maintainer per
# week as a reminder to review and approve the release PR, tag the release
# branch, and approve the marketplace-production deployment, then @mentions
# week as a reminder to review and approve the release PR and tag the release
# branch, then @mentions
# zoomote as the visible cue of who cuts the release. Webhook-posted mentions
# do not trigger Roomote (confirmed by test), so the release prep (release PR
# per .roo/commands/release.md, posted in the release channel) runs from the
Expand Down Expand Up @@ -63,13 +63,12 @@ jobs:
${on_deck} — reminder: you are on deck for this week's release. When the release PR is up:

1. Review and approve the release PR.
2. Tag the release branch tip (\`v[version]\`) to trigger the Marketplace publish workflow.
3. Approve the deployment when the \`marketplace-production\` environment requests it.
4. After publishing succeeds, add the release PR to the merge queue.
2. Tag the release branch tip (\`v[version]\`) to build the VSIX and attach it to the GitHub Release.
3. After the release workflow succeeds, add the release PR to the merge queue.

${ZOOMOTE_MENTION} prepare this week's Zoo Code release per \`.roo/commands/release.md\` and post the release PR in this channel.

Avoid merging or rebasing the release branch before publishing, so the approved tag keeps the intended commit SHA.
Avoid merging or rebasing the release branch before the VSIX release build completes, so the approved tag keeps the intended commit SHA.

More detail: https://discord.com/channels/1497384592494297201/1498024845945081999/1512914847124291667
EOF
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/release-validation.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ on:
- "webview-ui/src/components/chat/Announcement.tsx"
- "releases/**"
- ".github/workflows/release-validation.yml"
- ".github/workflows/release-vsix.yml"

# Cancel superseded runs when a pull request is updated. Non-PR events keep
# unique groups, so manual runs are never cancelled.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
name: Publish Stable Extension
name: Build Stable VSIX Release

on:
push:
tags:
- "v*.*.*"
workflow_dispatch:

# Least privilege: publish-stable escalates to contents: write via its own
# job-level permissions block.
# Least privilege: build-stable-release escalates to contents: write to create
# the GitHub release and attach the VSIX.
permissions:
contents: read

Expand All @@ -28,7 +28,7 @@ jobs:
--jq '.[0].number // empty')

if [ -z "$pr_number" ]; then
echo "No PR found for commit ${SHA}. Deployment requires an approved PR."
echo "No PR found for commit ${SHA}. Release requires an approved PR."
exit 1
fi

Expand All @@ -49,16 +49,15 @@ jobs:
echo "PR #${pr_number} review_decision: ${review_decision}"

if [ "$review_decision" != "APPROVED" ]; then
echo "PR #${pr_number} is not approved (state: ${review_decision}). Deployment blocked."
echo "PR #${pr_number} is not approved (state: ${review_decision}). Release blocked."
exit 1
fi

echo "PR #${pr_number} is approved. Proceeding."
echo "PR #${pr_number} is approved. Building release."

publish-stable:
build-stable-release:
needs: [check-pr-approval]
runs-on: ubuntu-latest
environment: marketplace-production
permissions:
contents: write

Expand All @@ -79,10 +78,10 @@ jobs:
test "$package_name" = "zoo-code"
test "$publisher" = "ZooCodeOrganization"

- name: Validate publish ref
- name: Validate release ref
run: |
if [ "$GITHUB_EVENT_NAME" = "workflow_dispatch" ] && [ "$GITHUB_REF_NAME" != "main" ]; then
echo "Manual stable publishes must run from main, not ${GITHUB_REF_NAME}."
echo "Manual stable release builds must run from main, not ${GITHUB_REF_NAME}."
exit 1
fi

Expand Down Expand Up @@ -132,23 +131,7 @@ jobs:
test "$artifact_name" = "zoo-code"
test "$artifact_publisher" = "ZooCodeOrganization"

- name: Publish to VS Code Marketplace
env:
VSCE_PAT: ${{ secrets.VSCE_PAT }}
run: |
package_version=$(node -p "require('./src/package.json').version")
npx @vscode/vsce publish --packagePath "bin/zoo-code-${package_version}.vsix"
echo "Published ZooCodeOrganization.zoo-code ${package_version} to VS Code Marketplace"

- name: Publish to Open VSX Registry
env:
OVSX_PAT: ${{ secrets.OVSX_PAT }}
run: |
package_version=$(node -p "require('./src/package.json').version")
pnpm exec ovsx publish "bin/zoo-code-${package_version}.vsix" --skip-duplicate
echo "Published ZooCodeOrganization.zoo-code ${package_version} to Open VSX Registry"

- name: Create GitHub release
- name: Create GitHub release and attach VSIX
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
Expand Down
26 changes: 13 additions & 13 deletions .roo/commands/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ mode: code

6. Write the release notes directly into `CHANGELOG.md` on the release branch.

- Use the heading format `## [version]` (with square brackets) — e.g. `## [3.58.1]`. The publish workflow at `.github/workflows/marketplace-publish.yml` extracts release notes by matching this exact pattern; headings without brackets will be missed and the GitHub release will fall back to a generic message.
- Use the heading format `## [version]` (with square brackets) — e.g. `## [3.58.1]`. The release workflow at `.github/workflows/release-vsix.yml` extracts release notes by matching this exact pattern; headings without brackets will be missed and the GitHub release will fall back to a generic message.
- Always include contributor attribution and the PR number: use `(PR #<prNumber> by @username)`.
- For PRs that close issues, include both issue and PR authors: `- Fix: Description (#123 by @reporter, PR #456 by @contributor)`.
- For PRs without linked issues, include the PR number and author: `- Add support for feature (PR #456 by @contributor)`.
Expand Down Expand Up @@ -84,7 +84,7 @@ mode: code

11. Once the release PR is open and passing checks, get it approved by a reviewer before proceeding.

- Do not create the tag until the PR has at least one approval — the publish workflow enforces this automatically and will fail if no approved PR is found for the tagged commit.
- Do not create the tag until the PR has at least one approval — the release workflow enforces this automatically and will fail if no approved PR is found for the tagged commit.

12. After the PR is approved, create the release tag on the release branch tip and push it:

Expand All @@ -94,27 +94,27 @@ mode: code
```

- Tag the branch tip as-is. Do not rebase or merge additional commits into the release branch before tagging — doing so changes the commit SHA and may pull in unreviewed changes that weren't part of the approval.
- The publish workflow validates that the tag version matches `src/package.json`.
- The release workflow validates that the tag version matches `src/package.json`.

13. The tag push triggers the stable publish workflow.
13. The tag push triggers the stable VSIX release workflow.

- The workflow first checks that the tagged commit belongs to an approved PR. If the PR is not yet approved this step fails — approve the PR first, then retrigger by recreating and pushing the tag: `git tag -d v[version] && git push origin :refs/tags/v[version] && git tag v[version] && git push origin v[version]`.
- Once the approval check passes, the `marketplace-production` environment gate fires and notifies the configured approvers.
- A human approver must then approve the deployment before the extension is published to VS Code Marketplace and Open VSX.
- The workflow checks that the tagged commit belongs to an approved PR, validates the tag against `src/package.json`, builds the VSIX, and creates the GitHub Release with the VSIX attached.
- If the PR is not yet approved, the workflow fails — approve the PR first, then retrigger by recreating and pushing the tag: `git tag -d v[version] && git push origin :refs/tags/v[version] && git tag v[version] && git push origin v[version]`.
- This workflow only builds and attaches the VSIX; it does not publish to the VS Code Marketplace or Open VSX.

14. After a successful deployment, add the release PR to the merge queue.
14. After the GitHub Release has been created with the VSIX attached, add the release PR to the merge queue.

```bash
gh pr merge [pr-number] --auto --squash
```

- Do not merge before the deployment succeeds — merging first and then discovering a publish failure leaves `main` ahead of what was actually shipped.
- Do not merge before the release workflow succeeds — merging first and then discovering a build failure leaves `main` ahead of the release artifact.
- The merge queue runs all required checks against the release branch before merging to `main`.

15. As the final stable extension release step, open a separate documentation PR in `Zoo-Code-Org/Zoo-Code-Docs`.

- Run this step only after the marketplace workflow for the exact stable tag has succeeded, the corresponding GitHub release exists, and step 14 has added the Zoo Code release PR to the merge queue. This step does not apply to nightly, CLI, npm, or types releases.
- Retain the exact Zoo Code changelog section, complete merged-PR inventory, release PR URL, tag and GitHub release URL, marketplace workflow URL, successful publication timestamp, and release PR merge-queue state as inputs to the docs work and final report.
- Run this step only after the VSIX release workflow for the exact stable tag has succeeded, the corresponding GitHub release with the VSIX exists, and step 14 has added the Zoo Code release PR to the merge queue. This step does not apply to nightly, CLI, npm, or types releases.
- Retain the exact Zoo Code changelog section, complete merged-PR inventory, release PR URL, tag and GitHub release URL, VSIX release workflow URL, release creation timestamp, and release PR merge-queue state as inputs to the docs work and final report.

**Preflight and checkout**

Expand Down Expand Up @@ -160,9 +160,9 @@ mode: code

- Inspect build warnings explicitly. Block the PR on newly introduced broken-link, document, MDX, sidebar, or content warnings. Verify the changed and staged scope contains only intended source files and no generated output.
- Commit as `docs(release): document v[version]`, push normally (never force-push) to `docs/release-v[version]`, and stop rather than overwrite a remote race.
- Open or reuse a PR in `Zoo-Code-Org/Zoo-Code-Docs` with base `main` and title `[Docs] Update documentation for Zoo Code v[version]`. Its body must include the source release and tag, Zoo Code release PR, marketplace workflow and successful publication timestamp, summary, package version synchronization, per-PR impact matrix and exclusions, evergreen changes or no-change rationale, validation results and warning review, and an explicit statement that this is a separate docs PR and will not be auto-merged. Never enable auto-merge for this PR.
- Open or reuse a PR in `Zoo-Code-Org/Zoo-Code-Docs` with base `main` and title `[Docs] Update documentation for Zoo Code v[version]`. Its body must include the source release and tag, Zoo Code release PR, VSIX release workflow and release creation timestamp, summary, package version synchronization, per-PR impact matrix and exclusions, evergreen changes or no-change rationale, validation results and warning review, and an explicit statement that this is a separate docs PR and will not be auto-merged. Never enable auto-merge for this PR.

**Reporting and partial failure**

- Docs failure cannot roll back or invalidate the published extension. A failure report must begin: `Zoo Code v[version] is already published and docs PR completion is pending.` Then report the failed checkpoint, checkout path, branch, PR URL/state when present, failure details, and the safe recovery action.
- The final release report must include release/tag/workflow URLs and the successful publication timestamp, the Zoo Code release PR merge-queue state, docs PR URL/state, docs branch and commit SHA, package-version synchronization status, release-note/index/sidebar status, evergreen documentation status, validation results and inspected warnings, and confirmation that the separate docs PR was not auto-merged.
- The final release report must include release/tag/workflow URLs and the release creation timestamp, the Zoo Code release PR merge-queue state, docs PR URL/state, docs branch and commit SHA, package-version synchronization status, release-note/index/sidebar status, evergreen documentation status, validation results and inspected warnings, and confirmation that the separate docs PR was not auto-merged.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Zoo Code Changelog

## [3.94.1]
- Workspace provider isolation by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/1
- Ref #2303: Use bracket access in provider tests by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/2
- Fix invalid custom storage setting fallback by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/3
- Workspace provider isolation by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/5

## [3.94.0]

- ✨ **Broader model and provider support:** Use Claude Haiku 5.5 through Anthropic, send images to compatible VS Code LM models, tune temperature for OpenCode Go Responses models, and cancel requests cleanly across more providers.
Expand Down
1 change: 1 addition & 0 deletions packages/types/src/global-settings.ts
Original file line number Diff line number Diff line change
Expand Up @@ -187,6 +187,7 @@ export const globalSettingsSchema = z.object({
allowedMaxCost: z.number().nullish(),
autoCondenseContext: z.boolean().optional(),
autoCondenseContextPercent: z.number().optional(),
disableAutoContextManagement: z.boolean().optional(),

/**
* Whether to include current time in the environment details
Expand Down
1 change: 1 addition & 0 deletions packages/types/src/vscode-extension-host.ts
Original file line number Diff line number Diff line change
Expand Up @@ -412,6 +412,7 @@ export type ExtensionState = Pick<

autoCondenseContext: boolean
autoCondenseContextPercent: number
disableAutoContextManagement: boolean
marketplaceItems?: MarketplaceItem[]
// eslint-disable-next-line @typescript-eslint/no-explicit-any
marketplaceInstalledMetadata?: { project: Record<string, any>; global: Record<string, any> }
Expand Down
7 changes: 7 additions & 0 deletions src/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Zoo Code Changelog

## [3.94.1]

- Workspace provider isolation by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/1
- Ref #2303: Use bracket access in provider tests by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/2
- Fix invalid custom storage setting fallback by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/3
- Workspace provider isolation by @FullstackSensei in https://github.com/FullstackSensei/Zoo-Code/pull/5

## [3.94.0]

- ✨ **Broader model and provider support:** Use Claude Haiku 5.5 through Anthropic, send images to compatible VS Code LM models, tune temperature for OpenCode Go Responses models, and cancel requests cleanly across more providers.
Expand Down
90 changes: 88 additions & 2 deletions src/core/config/ProviderSettingsManager.ts
Original file line number Diff line number Diff line change
@@ -1,4 +1,7 @@
import * as crypto from "node:crypto"
import * as path from "node:path"
import { ExtensionContext } from "vscode"
import * as vscode from "vscode"
import { z, ZodError } from "zod"
import deepEqual from "fast-deep-equal"

Expand All @@ -20,6 +23,7 @@ import { TelemetryService } from "@roo-code/telemetry"
import { Mode, modes } from "../../shared/modes"
import { buildApiHandler } from "../../api"
import { disposeApiHandler } from "../../api/dispose-api-handler"
import { Package } from "../../shared/package"
import { downgradeLegacyRooConfig } from "./routerRemoval"

// Type-safe model migrations mapping
Expand Down Expand Up @@ -57,7 +61,9 @@ export type ProviderProfiles = z.infer<typeof providerProfilesSchema>

export class ProviderSettingsManager {
private static readonly SCOPE_PREFIX = "roo_cline_config_"
private static readonly LEGACY_SECRET_STORAGE_KEY = `${ProviderSettingsManager.SCOPE_PREFIX}api_config`
private readonly defaultConfigId = this.generateId()
private readonly customStoragePath: string

private readonly defaultModeApiConfigs: Record<string, string> = Object.fromEntries(
modes.map((mode) => [mode.slug, this.defaultConfigId]),
Expand All @@ -80,8 +86,11 @@ export class ProviderSettingsManager {

private readonly context: ExtensionContext

constructor(context: ExtensionContext) {
constructor(context: ExtensionContext, customStoragePath?: string) {
this.context = context
this.customStoragePath = ProviderSettingsManager.normalizeCustomStoragePath(
customStoragePath ?? ProviderSettingsManager.getConfiguredCustomStoragePath(),
)

// TODO: We really shouldn't have async methods in the constructor.
this.initialize().catch(console.error)
Expand Down Expand Up @@ -653,12 +662,89 @@ export class ProviderSettingsManager {
})
}

private static getConfiguredCustomStoragePath(): string {
try {
const configuration = vscode.workspace.getConfiguration(Package.name)
const customStoragePath = configuration.get<unknown>("customStoragePath", "")
return typeof customStoragePath === "string" ? customStoragePath : ""
} catch {
return ""
}
}

private static normalizeCustomStoragePath(customStoragePath?: string): string {
const value = customStoragePath?.trim() ?? ""
if (!value) {
return ""
}

const isWindowsLike = value.includes("\\") || /^[A-Za-z]:[\\/]/.test(value)
const normalized = isWindowsLike ? path.win32.normalize(value).replace(/\\/g, "/") : path.normalize(value)
const absolute = isWindowsLike
? path.win32.isAbsolute(value)
? path.win32.normalize(value)
: path.win32.resolve(value)
: path.isAbsolute(normalized)
? normalized
: path.resolve(normalized)

if (isWindowsLike) {
return absolute.replace(/\\/g, "/").replace(/^([A-Za-z]):/, (_, drive: string) => `${drive.toLowerCase()}:`)
}

return absolute
}

private get isCustomStorageScoped() {
return Boolean(this.customStoragePath)
}

private get migrationMarkerKey() {
return `${this.secretsKey}:migration-complete`
}

private get legacySecretsKey() {
return ProviderSettingsManager.LEGACY_SECRET_STORAGE_KEY
}

private get secretsKey() {
return `${ProviderSettingsManager.SCOPE_PREFIX}api_config`
if (!this.customStoragePath) {
return this.legacySecretsKey
}

return `${ProviderSettingsManager.SCOPE_PREFIX}api_config_${crypto
.createHash("sha256")
.update(this.customStoragePath)
.digest("hex")}`
}

private async ensureStorageScopeMigration() {
if (!this.isCustomStorageScoped) {
return
}

const migrationComplete = await this.context.globalState.get<boolean>(this.migrationMarkerKey)
if (migrationComplete === true) {
return
}

const scopedConfig = await this.context.secrets.get(this.secretsKey)
if (scopedConfig) {
await this.context.globalState.update(this.migrationMarkerKey, true)
return
}

const legacyConfig = await this.context.secrets.get(this.legacySecretsKey)
if (legacyConfig) {
await this.context.secrets.store(this.secretsKey, legacyConfig)
}

await this.context.globalState.update(this.migrationMarkerKey, true)
}

private async load(): Promise<ProviderProfiles> {
try {
await this.ensureStorageScopeMigration()
const content = await this.context.secrets.get(this.secretsKey)

if (!content) {
Expand Down
Loading
Loading