Pull Request

Description

Fixes HTTP 422 error "Cannot upload assets to an immutable release" when uploading VSIX to GitHub releases. The repository has GitHub's immutable releases feature enabled, which prevents modifications to published releases.

This PR:

• Configures release-please to create draft releases by adding "draft": true at the root level of release-please-config.json (applies globally to all packages)
• Adds a publish step in the workflow that runs after VSIX upload using gh release edit --draft=false

Note: The "draft": true setting is placed at the root level rather than under packages["."] because release-please supports both locations, and root-level applies the setting globally. Since this repository has a single package, root-level placement is cleaner and functionally equivalent.

Related Issue(s)

Fixes #335

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Testing

• Validated workflow syntax with linting
• Verified gh release edit --draft=false command syntax against GitHub CLI documentation
• Reviewed release-please documentation confirming draft config option behavior at both root and package levels

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege

Additional Notes

The workflow uses the existing github.token which already has contents: write permission configured in the publish-extension job.