Repository navigation
ci: publish the raw corpus archive with every tag - #258
Merged
Merged
Conversation
…fact interscript-maps-isc-<version>.tar.gz + sha256, built with git archive from the pushed sha (maps/ + libs/, the .isc corpus the ruby/ts/rust runtimes resolve). The v3.0.0 release already carries both archives; this makes every future tag ship the same pair.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Gems, npm and crates consumers all resolve the raw .isc corpus; the release previously shipped only the compiled JSON-IR tar. Every tag now attaches interscript-maps-isc-.tar.gz + sha256 (git archive of maps/ + libs/ at the pushed commit) next to the IR artifact. Already applied retroactively to the v3.0.0 release.