Publish regular pre-release builds to VS Code Marketplace
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript, vscode
Research direction
Start by inspecting the existing workflow that publishes a development VSIX on pushes to master and how it invokes vsce. Define and document a Marketplace-compatible 3.x pre-release version scheme, automate regular publishing with vsce publish --pre-release, and verify that stable release publishing remains unchanged.
Written by the indexing model from the issue text.
Description
We currently publish a development VSIX to a GitHub pre-release on every push to master, but users cannot opt into automatic pre-release updates through the VS Code Marketplace.
We cannot simply publish the current version such as 3.0.0-rc.0: Marketplace pre-releases still require a plain major.minor.patch version and do not support SemVer pre-release identifiers.
I propose that we:
- define a Marketplace-compatible versioning scheme for 3.x pre-releases;
- regularly publish development builds with
vsce publish --pre-release; - keep normal stable releases unchanged.
This would make testing upcoming 3.x releases much easier without requiring users to manually download and install VSIX files.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 23h 31m
- Merged PRs (30d)
- 13
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from REditorSupport/vscode-R
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
REditorSupport/vscode-R#1687 · 4 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
REditorSupport/vscode-R#1763 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
REditorSupport/vscode-R#1755 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
REditorSupport/vscode-R#1749 · 5 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
REditorSupport/vscode-R#1740 · 2 comments ·
Maintainers usually reply within 1 day
All issues in REditorSupport/vscode-R
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
opengovsg/FormSG#10118 · 1 comment ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude
Difficulty 1/5 Under an hour Newbie friendliness 75/100
linagora/twake-calendar-frontend#1434 · 1 comment ·
Maintainers usually reply within 1 day
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
iptv-org/iptv#52824 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
jaegertracing/jaeger-ui#4512 ·
Maintainers usually reply within 1 day
-
area:ide documentation enhancement platform:macos platform:vscode
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anthropics/claude-code#97389 ·
Maintainers usually reply within 1 day