Update static.zip, automate its release process #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dev.js
entrypoint has been updated to include the recent JavaScriptKit runtime fix: swiftwasm/JavaScriptKit#19I've also added a new subcommand to
carton-release
, which is now able to automaticallly create a newstatic.zip
and record updated hashes in the source code. It still doesn't upload the archive automatically to previous release assets, but I wonder if that should be done manually anyway, at least until we have some kind of tests that verify the whole process end-to-end.Additionally, since the new runtime is not compatible with the old Swift parts of JavaScriptKit,
carton dev
now checks the revision of JavaScriptKit that projects have specified in theirPackage.swift
. It doesn't block the build process, but I hope it gives enough warning about the incompatibility.