Add instruction to update bazel workspace in emsdk (emscripten-core#12164) [ci skip]

walkingeyerobot · web-flow · commit dce751f2a877 · 2020-09-15T12:41:41.000-07:00
diff --git a/docs/process.md b/docs/process.md
@@ -61,9 +61,11 @@ How:
    adding the version and the hash. Updating the "latest" tag there to the new
    release is possible, but can also be deferred if you want to do more testing
    before users fetching "latest" get this release.
-2. Tag the emsdk repo as well, on the commit that does the update, after it
+2. Run [update_bazel_workspace.sh](https://github.com/emscripten-core/emsdk/blob/master/scripts/update_bazel_workspace.sh).
+   This will update the bazel toolchain based on the new "latest" tag in emscripten-releases-tags.txt.
+3. Tag the emsdk repo as well, on the commit that does the update, after it
    lands on master.
-3. Update
+4. Update
    [emscripten-version.txt](https://github.com/emscripten-core/emscripten/blob/master/emscripten-version.txt)
    in the emscripten repo. This is a delayed update, in that the tag will refer
    to the actual release, but the update to emscripten-version.txt is a new
@@ -74,7 +76,7 @@ How:
      when that's unlikely, etc.
    * There is no need to open a PR for this change, you can optionally just
      commit it directly.
-4. Tag the emscripten repo on the emscripten commit on which
+5. Tag the emscripten repo on the emscripten commit on which
    `emscripten-version.txt` was updated. (This could also be the commit from the
    DEPS file as well, but this way is less confusing when just working on the
    emscripten repo, and the difference should only be one commit anyhow.)
