Repository navigation
chore: release - #58
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 02:00
7f714d9 to
7a6ac1f
Compare
amritk
approved these changes
Nov 13, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 02:00
7a6ac1f to
772b58d
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@scalar/ruby-fmt@0.9.0
Minor Changes
55fab33: Breaking.
@scalar/ruby-fmtis nowrubocop --autocorrect --only Layoutand nothing else, byte-identical to RuboCop 1.92.2. The reprinting pass that ran before it, on a CRuby VM compiled to wasm, is gone, and with it theruby_fmt.wasm.brartifact and the@ruby/wasm-wasidependency.What the formatter does now: it corrects Layout - indentation, alignment, blank lines, spacing and line length - within the line structure it is given. What it no longer does: reprint. It does not move statements onto lines of their own, so
def x; a; b; endcomes out as it went in. It suits input that already has its line structure, such as generated code, and output changes for any input whose line breaking the reprinter used to change.printWidthis nowLayout/LineLength'sMax, and defaults to 120 (it was 80). 120 is RuboCop's own default, so with no options the output is exactly what stock RuboCop writes; 80 was the old reprinter's width and now would only make the cop rebreak more of the line structure the caller chose. The cop's autocorrect only breaks at argument lists, collection literals and block braces, so a long string literal or constant assignment stays long, and a broken line can still be over the limit. ALayout/LineLengthentry inrubocopConfigwins overprintWidth.rubocop: falsethrows aTypeErrorinstead of meaning "reprint only". There is nothing left to run without RuboCop.break if a; b = 1) through insidebegin … end, where RuboCop flags it and then reports an infinite loop; the package now rejects such a file the same way.formatSyncneeds noinit()under Node, and never refuses for memory: the module is read, decompressed, compiled and instantiated synchronously, and recovering from a crash in the pass is synchronous too.initstays, and is optional under Node. In a browser,formatSyncstill needs oneawait init().inittakes{ url, bytes, encoding }forrbcop_fmt.wasm.br, at the top level.init({ rbcop: { … } })throws, and a top-levelurlno longer means the removed artifact.@scalar/ruby-fmt/wasmresolves torbcop_fmt.wasm.br.@scalar/ruby-fmt/rbcop-wasmstill does too.rbcop now builds from upstream (costajohnt/rbcop), at the merge that carries the
case/inguard fix the build previously took from a fork. That switch on its own changes no code: built from either, the artifact is byte for byte the same.