emscripten-releases-tags.txt

{
  "latest": "1.38.34",
  "releases": {
    "1.38.34": "048cf9424790cc525a7ea6da340820aae226f3b9",
    "1.38.33": "3b8cff670e9233a6623563add831647e8689a86b"
  }
}
Prepare for emscripten-releases (#237) Updated to our current initial plan here: * Add emscripten-releases-tags.txt which is a JSON file with a map of tag name to git hash in the emscripten-releases repo. Right now this file is just checked in here; in the future we may make the emsdk update it from git tags with update-tags etc. * That file contains a "latest" tag, which is fetched for when getting latest-releases-[upstream\|fastcomp]. We may want that to eventually be updated based on the latest green stuff on the bots perhaps. * Rename the current sdk-[upstream\|fastcomp]-* etc. to sdk-waterfall-[upstream\\|fastcomp]-. Then we'll have sdk-releases-[upstream\|fastcomp]- etc. This is just an internal name change - emsdk install latest-upstream still works as before, and still uses the waterfall (so we don't break our github CI). * Add support for emsdk install latest-releases-[upstream\\|fastcomp] * Add a test using the actual emscripten-releases builds 2019-05-22 17:23:04 -07:00			`{`
Tag 1.38.34 (#258) This should fix some version warnings people are currently seeing - we removed the fastcomp version warnings between repos check after the last version, in emscripten-core/emscripten#8664, #259 2019-06-02 09:11:46 -07:00			`"latest": "1.38.34",`
Add emscripten-releases support for release tags (#243) * Structures emscripten-releases-tags.txt to mention the latest release, and then a list of all previous releases. * Adds a new release for 1.38.33. * If the manifest has emscripten_releases_hash, then we write out emscripten-version.txt with the proper version. We start with the hash, and check if there is a released version for it, if so we emit that, otherwise we emit the hash. * Windows zipfile fix. 2019-05-23 17:08:23 -07:00			`"releases": {`
Tag 1.38.34 (#258) This should fix some version warnings people are currently seeing - we removed the fastcomp version warnings between repos check after the last version, in emscripten-core/emscripten#8664, #259 2019-06-02 09:11:46 -07:00			`"1.38.34": "048cf9424790cc525a7ea6da340820aae226f3b9",`
Add emscripten-releases support for release tags (#243) * Structures emscripten-releases-tags.txt to mention the latest release, and then a list of all previous releases. * Adds a new release for 1.38.33. * If the manifest has emscripten_releases_hash, then we write out emscripten-version.txt with the proper version. We start with the hash, and check if there is a released version for it, if so we emit that, otherwise we emit the hash. * Windows zipfile fix. 2019-05-23 17:08:23 -07:00			`"1.38.33": "3b8cff670e9233a6623563add831647e8689a86b"`
			`}`
Prepare for emscripten-releases (#237) Updated to our current initial plan here: * Add emscripten-releases-tags.txt which is a JSON file with a map of tag name to git hash in the emscripten-releases repo. Right now this file is just checked in here; in the future we may make the emsdk update it from git tags with update-tags etc. * That file contains a "latest" tag, which is fetched for when getting latest-releases-[upstream\|fastcomp]. We may want that to eventually be updated based on the latest green stuff on the bots perhaps. * Rename the current sdk-[upstream\|fastcomp]-* etc. to sdk-waterfall-[upstream\\|fastcomp]-. Then we'll have sdk-releases-[upstream\|fastcomp]- etc. This is just an internal name change - emsdk install latest-upstream still works as before, and still uses the waterfall (so we don't break our github CI). * Add support for emsdk install latest-releases-[upstream\\|fastcomp] * Add a test using the actual emscripten-releases builds 2019-05-22 17:23:04 -07:00			`}`