@@ -210,7 +210,8 @@ Release process is handled by `release`, `dist` and `promote` xtasks, `release`
210210./rust-rust-analyzer # Note the name!
211211```
212212
213- Additionally, it assumes that the remote for ` rust-analyzer ` is called ` upstream ` (I use ` origin ` to point to my fork).
213+ The remote for ` rust-analyzer ` must be called ` upstream ` (I use ` origin ` to point to my fork).
214+ In addition, for ` xtask promote ` (see below), ` rust-rust-analyzer ` must have a ` rust-analyzer ` remote pointing to this repository on GitHub.
214215
215216` release ` calls the GitHub API calls to scrape pull request comments and categorize them in the changelog.
216217This step uses the ` curl ` and ` jq ` applications, which need to be available in ` PATH ` .
@@ -225,13 +226,13 @@ Release steps:
225226 * push it to ` upstream ` . This triggers GitHub Actions which:
226227 * runs ` cargo xtask dist ` to package binaries and VS Code extension
227228 * makes a GitHub release
228- * pushes VS Code extension to the marketplace
229+ * publishes the VS Code extension to the marketplace
229230 * call the GitHub API for PR details
230231 * create a new changelog in ` rust-analyzer.github.io `
2312323 . While the release is in progress, fill in the changelog
2322334 . Commit & push the changelog
2332345 . Tweet
234- 6 . Inside ` rust-analyzer ` , run ` cargo xtask promote ` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule .
235+ 6 . Inside ` rust-analyzer ` , run ` cargo xtask promote ` -- this will create a PR to rust-lang/rust updating rust-analyzer's subtree .
235236 Self-approve the PR.
236237
237238If the GitHub Actions release fails because of a transient problem like a timeout, you can re-run the job from the Actions console.
0 commit comments