Repository navigation
ci: publish daily Marketplace pre-releases with odd minor versions - #1833
Conversation
renkun-ken
left a comment
There was a problem hiding this comment.
Reviewed c00f3ccfa6e6ff7fc6b8419cf944c131675cc26b. I found no blocking defects in the changed code. The odd/even minor scheme, packaging-only version rewrite, verification gates, and duplicate handling are consistent with #1751.
Validation:
- All five extension-version tests passed.
- Packaged the PR revision with
vsce package --pre-release --no-dependencies, confirmed version3.1.20261006andMicrosoft.VisualStudio.Code.PreRelease=truein the VSIX, and passed the packaged sess source-identity check. - Executed the actual
prepareshell step with mocked GitHub API responses for seven cases: first publication, unchanged revision, changed revision, retry retaining its original date, retry older than a successful run, an already-covered date, and a change after a skipped day.
The existing Copilot permission finding appears to be a false positive. The pinned artifact action authenticates uploads with ACTIONS_RUNTIME_TOKEN, rather than GITHUB_TOKEN; actions: write is not needed for this upload. Keep the current permissions. The overview's status-filter concern also does not apply: the workflow-runs API explicitly accepts conclusions such as status=success, which I also verified against the repository's runs.
Build, lint, Linux tests, and Windows tests have passed; macOS tests were still pending when checked. Actual scheduled execution and registry publication still need to be verified after merging.
|
@eitsupi Is it possible to trigger the pre-release somehow so that we can check if the publishing works properly? |
I deliberately didn't add a workflow dispatch trigger this time, but I think it would be fine to add one. |

Closes #1751.
Publish daily pre-releases to the VS Code Marketplace so users can receive development updates automatically.
3.1.YYYYMMDDby rewritingpackage.jsononly during packaging. Stable patch releases remain independent.package.json.The workflow reuses
VSCE_TOKEN. Retries retain the original UTC build date and tolerate an already-published version.