Fix broken links to emsdk (emscripten-core#15196)

gl84 · web-flow · commit 4fcbf0239ccc · 2021-10-01T07:07:23.000-07:00
diff --git a/docs/packaging.md b/docs/packaging.md
@@ -46,7 +46,7 @@ Alternatively, you may want to build our official emscripten release tags, which
 are the versions the emsdk lets users install. To find the mapping between the
 emsdk versions and the revision of the emscripten-releases repository, the emsdk
 has
-[emscripten-releases-tags.txt](https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.txt).
+[emscripten-releases-tags.json](https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.json).
 All versions listed there should be safe to build, as we check that the CI
 was green on them.
 
diff --git a/docs/process.md b/docs/process.md
@@ -54,7 +54,7 @@ Requirements:
 How:
 
 1. Run [`./scripts/create_release.py`][create_release] in the emsdk repository.
-   This script will update [emscripten-releases-tags.txt][emscripten_releases_tags],
+   This script will update [emscripten-releases-tags.json][emscripten_releases_tags],
    adding a new version.  You can either specify the desired hash, or let the
    script pick the current tot build.  The script will create a new git branch
    that can be uploaded as a PR.
@@ -131,5 +131,5 @@ See notes above on installing sphinx.
 [emscripten_version]: https://github.com/emscripten-core/emscripten/blob/main/emscripten-version.txt
 [changelog]: https://github.com/emscripten-core/emscripten/blob/main/ChangeLog.md
 [create_release]: https://github.com/emscripten-core/emsdk/blob/main/scripts/create_release.py
-[emscripten_releases_tags]: https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.txt
+[emscripten_releases_tags]: https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.json
 [DEPS]: https://chromium.googlesource.com/emscripten-releases/+/refs/heads/master/DEPS
diff --git a/site/source/docs/contributing/developers_guide.rst b/site/source/docs/contributing/developers_guide.rst
@@ -120,13 +120,13 @@ the build succeeded). Each build is identified by a hash (a long string of numbe
 and characters), which is a hash of a commit in the
 `releases repo <https://chromium.googlesource.com/emscripten-releases>`_.
 The mapping of Emscripten release numbers to such hashes is tracked by
-`emscripten-releases-tags.txt in the emsdk repo <https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.txt>`_.
+`emscripten-releases-tags.json in the emsdk repo <https://github.com/emscripten-core/emsdk/blob/main/emscripten-releases-tags.json>`_.
 
 With that background, the bisection process would look like this:
 
 1. Find the hashes to bisect between. You may already know them if you found
    the problem on ``tot`` builds. If instead you only know Emscripten version
-   numbers, use ``emscripten-releases-tags.txt`` to find the hashes.
+   numbers, use ``emscripten-releases-tags.json`` to find the hashes.
 2. Using those hashes, do a normal ``git bisect`` on the ``emscripten-releases``
    repo.
 3. In each step of the bisection, download the binary build for the current
