chore: bump bundled @styx-api/core to 0.9.0 - #17
Merged
Conversation
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
1 participant
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.
Bumps the in-browser compiler the hub bundles from 0.6.1 to 0.9.0, keeping niwrap.dev in snippet/command lockstep with the niwrap 1.1.0 release (styx-api/niwrap#333).
Without this, niwrap.dev keeps generating snippets with a compiler three minors behind the published package - notably reproducing the output-handling bugs fixed in #69/#70 and using the old anonymous-struct type names from before #81.
Verified locally:
npm run test(220 passing) andnpm run buildboth clean against 0.9.0.Merge after styx-api/niwrap#333 so the deployed hub does not get ahead of the published catalog.