Skip to content

fix: add PNG icon so vscode-k9 is publishable (#1)#8

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/missing-png-icon-issue-1
May 17, 2026
Merged

fix: add PNG icon so vscode-k9 is publishable (#1)#8
hyperpolymath merged 1 commit into
mainfrom
fix/missing-png-icon-issue-1

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Refs #1 (publish prep — removes the hard blocker)

package.json declares "icon": "icons/k9-icon.png" but only k9-icon.svg existed. The VS Code Marketplace rejects SVG icons, so vsce package fails outright — publishing was impossible regardless of the PAT.

This adds a faithful 128×128 RGBA PNG rendered from k9-icon.svg (same gradient/corners/wordmark), matching the format vscode-a2ml already ships. The SVG is kept as source.

After this merges, vscode-k9 is one step from done: vsce publish once the Azure DevOps PAT exists. See the readiness-audit comment on #1.

🤖 Generated with Claude Code

package.json declares "icon": "icons/k9-icon.png" but only k9-icon.svg
existed. The VS Code Marketplace rejects SVG icons, so `vsce package`
would fail outright — a hard publish blocker.

Add a 128x128 RGBA PNG rendered faithfully from k9-icon.svg (same
diagonal #4ad97a->#1a6a2e gradient, 16px rounded corners, white "K9"
wordmark + faint accents), matching the format vscode-a2ml already
ships (128x128 RGBA). icons/k9-icon.svg is retained as the source.

This removes the only packaging blocker; publishing is now a single
`vsce publish` once the Azure DevOps PAT is available (see issue).

Refs #1

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@hyperpolymath hyperpolymath merged commit a907a3d into main May 17, 2026
18 of 20 checks passed
@hyperpolymath hyperpolymath deleted the fix/missing-png-icon-issue-1 branch May 17, 2026 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant