Fix VS Code extension name conflict - #8
Conversation
- Set VS Code extension package.json name to unscoped 'vocadev-vscode-theme' - Add prepublishOnly and postpublish scripts to temporarily use '@M5Devs/vocadev-vscode-theme' during GitHub Packages publish - Update pnpm workspace filter references in workflow and documentation Co-authored-by: ClausValcaTD <193546948+ClausValcaTD@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Resolves the name conflict between VS Code extension packaging (which requires unscoped name 'vocadev-vscode-theme') and GitHub Packages (which requires scoped name '@M5Devs/vocadev-vscode-theme') by keeping the primary package name unscoped and temporarily setting the scoped name during publish lifecycle scripts. Also updates workspace filter references in the release workflow and documentation.
PR created automatically by Jules for task 3507359104720287572 started by @ClausValcaTD