Releases: Zokka-Dev/zokka-compiler
0.191.0-beta.0
The first beta release of 0.191.0. This is the same as 0.191.0-alpha.37. We just did some additional manual testing before releasing this.
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/9278834362. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.191.0-alpha.37
Final alpha release for 0.191.0 that bundles in the new package server.
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/9278343949. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.191.0-alpha.35
Fixing an npm packaging bug with 0.191.0-alpha.34
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7824126176. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.191.0-alpha.34
Changes since 0.191.0-alpha.27:
- Small optimization to code generated during TCO (removing an extraneous field in one of the intermediate JS objects created). There is still a larger code change needed to only apply the current TCO strategy in the presence of closures, to get better runtime performance.
- Finally have ARM64 builds for Mac! Still don't have Linux ARM64 builds unfortunately because it's very tricky to get Docker working on the current Mac M1 GitHub action runners. Debating among just waiting for GitHub to come out with Linux ARM64 runners (which should be on the horizon in the next few months), creating a private runner, and just eating the enormous performance hit and using QEMU emulation.
There is likely one more release before we leave alpha (mainly to support private repositories with token authentication), but we're close!
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7823674100. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.191.0-alpha.27
Functionality-wise, Zokka now enforces hashes for single-package-locations to make it easier to trust that the code you're getting is actually the code you were expecting. See https://github.com/Zokka-Dev/zokka-compiler/tree/745ee99c08bb063e16430e47ef9c0739e1c3a3e1#custom-single-file-repositories for an example of that. So far we only have SHA-1 hashes, but because SHA-1 is already being recognized as a bit of a substandard hash, I've put in a hash-type field to allow for future different kinds of hashes. I've gone with SHA-1 at the moment because that's currently what Elm is using for its own package server.
The jump in 12 version numbers is because of some CI/CD housekeeping (and a lot of frustrating revisions along the way), where now GitHub actions takes care of automatically publishing new versions to NPM simply via git tagging. This is to lay the foundations for other Zokka-Dev members to be able to publish easily and quickly. We don't want publication headaches to slow down bug fixes!
Because of that npx [email protected] should just work! (If you'd like you can do npx zokka as well, but sometimes NPM takes a little bit of time to update its caches as to what the latest version of zokka is).
This is hopefully the last breaking change to file formats and as such is likely the last alpha before our first beta release! And then if all goes well we'll have our first proper release in a few weeks from now.
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7619140606. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.191.0-alpha.15
We've switched to a new versioning scheme because npm only allows 3 elements of a version (e.g. 1.2.3 not 1.2.3.4). In this case -alpha counts as the last part and npm doesn't care about what comes next, so the .15 has no problem, but 0.19.1.0-alpha.5 would've caused issues because now the -alpha is in the fourth element.
In this release we also fix another codegen issue, this time elm-lang/elm-make#174 which is linked from elm/compiler#1377
We also do some minor housecleaning. The most exciting part of this release is that we're finally on npm! So if you just run npx zokka, you should be able to get things up and running immediately.
There's a small bug in the release pipeline right now, so that the linux build isn't getting its version attached to it. Otherwise the standard reproducibility bit is below:
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7416795321. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.19.1.0-alpha-10
Fix remaining corner cases with TCO
This release should fix all of the following outstanding issues in the
Elm issue tracker as verified by the test suite:
elm/compiler#2017
elm/compiler#1813
elm/compiler#2268
elm/compiler#2221
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7295492999. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.19.1.0-alpha-9
First major compiler bugfix release! We fix TCO issues in the Elm compiler. Still some questions around freshness of generated JS variables that I need to address.
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7268491038. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
0.19.1.0-alpha-8
This release is mainly some performance improvements. We make sure that we're using proper optimization settings when compiling the Zokka compiler. There was also an issue with how we were using the zokka-registry.dat file in ../zokka-cache (a cached representation of metadata concerning all your custom repositories) which made it so that we never actually used the cached value and instead re-calculated it from scratch each time! That has been fixed so that the cache is properly used.
If you have used a previous release of Zokka, you should make sure to delete your $ELM_HOME/0.19.1/zokka-cache folder (this does not contain your custom-repository-config.json file, which is under .../zokka).
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/Zokka-Dev/zokka-compiler/actions/runs/7241511248. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.
Alpha 6 release of Zokka
This is a naming change (that also changes the names in code and docs). We go from Zelm to Zokka after receiving feedback that we shouldn't use "elm" anywhere in the name.
Zokka is a nonsense word without much SEO conflict. Also fairly easy to pronounce in many languages.
All binaries associated with this release are built with GitHub actions and hence open to scrutiny at https://github.com/changlinli/zokka-compiler/actions/runs/7106177316. If you would like, you can verify that the hash of the artifacts generated by that workflow match the hashes of the files attached to this release. Note that workflow artifacts are only saved by GH for 90 days so if you come across this release > 90 days from the release date, you may no longer be able to perform this verification. We know this is not ideal and may try to fix in the future (but unfortunately no promises because CI/CD can be quite painful to deal with). Also note that the package sizes in the workflow may look different than the sizes attached here, because GH in workflows records the uncompressed size. If you download and compare the hashes they will be equal.