vscode-peacock

Fixes

• Fixed unfocused windows losing Peacock's status bar color: when peacock.affectStatusBar is enabled, Peacock now writes statusBar.inactiveBackground alongside the active status bar token so VS Code keeps the Peacock color even after the window loses focus (#773)
• Re-pinned @types/vscode to 1.49.0 (matching engines.vscode) so vsce packaging no longer fails with @types/vscode ... greater than engines.vscode ... when CI runs npm run package:check. Also told Dependabot to ignore @types/vscode until Peacock intentionally raises its minimum supported VS Code version, preventing the same incompatible bump from reopening CI failures.

Infrastructure

• Bumped morgan (transitive dev dependency) from 1.10.1 to 1.12.0, picking up fixes for log-injection CVEs in the :remote-user token and token value escaping (#760)
• Added a required main branch ruleset (the CI / build status check, plus automatic Copilot code review on every PR/push) now that CI passing is enforced before merge, not just advisory. Because ci.yml's build job previously used paths-ignore to skip docs/markdown-only changes, a docs-only PR could never satisfy this new required check and would be permanently blocked; ci.yml now always triggers and instead detects a docs-only diff internally (via dorny/paths-filter) to skip the actual lint/build/test steps while still reporting the same single build check. An initial fix using a second, docs-only-triggered workflow was reverted after code review flagged that a mixed docs+code PR would trigger both workflows and produce two ambiguous, identically-named CI / build checks.

Features

• Added a visual color picker to the Peacock: Change to a Favorite Color flow. The favorites Quick Pick now ends with a $(paintcan) Custom color… item that opens a webview with a native color well kept in sync with a hex/name/formula text field. Every edit previews live (the same way hovering a favorite already does, without unapplying your current color just from arrowing over the item), Apply keeps the color, and Cancel (or closing the panel) reverts to the color that was active before the picker opened. The Quick Pick now always opens, even with zero favorites saved, so the picker is reachable regardless (#708)
• Merged Peacock: Enter a Color with the visual picker into a single Peacock: Choose a Custom Color command: running it with no arguments now opens the Custom Color Picker directly, and its color field accepts every format the old input box did (hex, named colors, and rgb/rgba/hsl/hsla/hsv/hsva values), not just hex. The peacock.enterColor command ID is unchanged, so existing keybindings and scripts that invoke it programmatically with a color argument keep working exactly as before (#708 follow-up)
• Designed the color picker panel with a modern layout: a labeled color-well/field group, an eyedropper button (shown when the browser EyeDropper API is available) to sample any color from anywhere on screen, and a live title bar contrast preview — a sample swatch plus a WCAG contrast ratio badge — that reuses Peacock's own title-bar contrast logic, so a light custom color (e.g. orange or pink) is confirmed to get the same automatic dark-font contrast treatment as any other color, before you even apply it. The preview reflects your actual peacock.affectTitleBar/peacock.keepForegroundColor settings (with a note when the pairing doesn't apply), an invalid typed color (e.g. a color-name typo) marks the field invalid and disables Apply instead of doing nothing, Enter/Escape apply/cancel no matter which control has focus, and the panel's state (including the preview)

Fixes

• Fixed the currently-selected activity bar icon rendering VS Code's default gray instead of Peacock's colorized foreground under Modern UI's "activity bar on top" layout (and, more subtly, in the classic side layout too). Peacock now sets activityBar.activeBorder and activityBarTop.activeBorder explicitly to match the computed foreground (#652)

Docs

• Documented why a colored vertical line can appear between the side bar and editor with modernUI enabled — this is expected behavior when Peacock's affectEditorGroupBorder setting is on, not a bug (#652)

Full Changelog: https://github.com/johnpapa/vscode-peacock/compare/v4.4.0...v4.4.1

Features

• Added automatic migration that backs up existing workbench.colorCustomizations on first extension activation, preventing data loss when installing Peacock in workspaces with pre-existing color customizations. Users receive a notification with the option to view backed-up settings (#687)

Fixes

• Fixed a release-blocking vsce package failure: dependabot PR #733 bumped @types/vscode to ^1.134.0 without a corresponding engines.vscode bump, and vsce refuses to package when the declared type definitions are newer than the minimum VS Code version the extension claims to support (@types/vscode ^1.134.0 greater than engines.vscode ^1.49.0). Reverted @types/vscode to 1.49.0 to match the existing engines.vscode floor rather than raising the minimum supported VS Code version as a side effect of an unrelated dependency bump — Peacock's code doesn't use any VS Code API newer than 1.49.0
• Fixed title bar text readability on dark color schemes in Cursor IDE. Peacock now gates the mid-gray title bar foreground workaround (#647) behind a background.isLight() check, using adaptive light foreground (#e7e7e7) for dark schemes to maintain WCAG AA contrast ratios while preserving the toolbar icon visibility fix on light backgrounds (#700)
• Fixed a tinycolor2 CJS/ESM interop bug: color-library.ts's import * as tinycolor from 'tinycolor2' compiles to a raw require() under the project's classic (non-esModuleInterop) TypeScript/webpack build, but under Vite/esbuild's stricter ESM semantics a namespace import can never be callable, so any color-manipulation call built with Vite (including the new Vitest unit lane) failed with TypeError: ... is not a function. Switched to import tinycolor = require('tinycolor2'), which compiles identically (a plain require()) under both toolchains (#670)
• Reconciled the title bar foreground fix (#700) with the extracted getTitleBarForegroundForApp helper (#670) — the helper now takes the background color and applies the same light/dark gating as the host fix, instead of unconditionally overriding the Cursor foreground
• Removed the one-time workbench.experimental.modernUI compatibility notice. The root cause was upstream in VS Code: modern UI mode forced the title bar, activity bar, and status bar to transparent backgrounds/borders with !important, overriding Peacock's (and any theme's) color customizations — reported as microsoft/vscode#326126 "Some color theme settings and color customizations are ignored in modern UI mode", fixed by microsoft/vscode#329701 "Restore theme colors in Modern UI shell" (merged August 2026). This is confirmed by multiple independent user reports on #652, so the warning was no longer accurate and was confusing users (#711). Added a regression test asserting applyColor() writes an identical workbench.colorCustomizations payload whether modernUI is enabled or disabled, so Peacock's own write path stays provably UI-mode-agnostic. The first version of that test actually caught a bug in itself, not in Peacock: it compared VS Code's live WorkspaceConfiguration object directly, which carries get/has/inspect/update methods as own properties, so assert.deepStrictEqual failed on function-reference identity even though every real color value matched. Fixed by comparing plain data via getColorCustomizationConfigFromWorkspace() instead.

Docs

• Added a README comparison showing Peacock working identically in VS Code's classic UI and the new Modern UI, as a visual companion to the Modern UI compatibility fix above.
• Clarified `pea

Includes a one-time in-product notice when workbench.experimental.modernUI is enabled, docs FAQ update, changelog entry, regression tests, and packaging fix to exclude e2e screenshots so VSIX is small (~243KB). PRs: #682 (notice/docs/tests), #683/#684/#685 (.vscodeignore and packaging). Tracking issue: #652.