release: sign the vsix build artifact
Open
blocked
feature-request
technical-debt
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
Acceptance Criteria
* We are able to sign the vsix file that we plan to distribute
* signing is either automated, or documented (internally) how to do, until we're able to automate it
Contributes to #9
Contributor guide
Research direction
Start by locating the VSIX packaging and release workflow, then read any existing signing guidance or configuration. Done means the distributable VSIX can be signed through automation, or the internal signing procedure is documented clearly enough to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- build-system, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100