Crystal Releases

Crystal 1.21.0 is released!

2026-07-16T00:00:00+00:00

We are announcing a new Crystal release 1.21.0 with several new features and bug fixes.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 161 changes since 1.20.3 by 21 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

Below we list the most remarkable changes in the language, compiler, and stdlib. For more details, visit the full changelog.

We expect little disruption from the introduction of execution contexts. But it can break code with specific expectations about concurrent behaviour, especially about the fact that a fiber stays on the same thread. Read more about this in the next section.

Another breaking change is that we disabled the automatic fallback to legacy PCRE, which has been deprecated for many years now. You can still explicitly opt-in with compiler flag -Duse_pcre or environment variable USE_PCRE1=1 (#16924).

Thanks, @straight-shoota

If you notice any unexpected issues, please let us know in the issue tracker or forum.

Execution contexts from RFC 0002 are enabled by default. We have written an entire blog post about it: Releasing Execution Contexts.

The default context has parallelism 1, i.e. it is single-threaded. It can be explicitly resized to run multiple fibers in parallel, or you can create additional contexts for parallelism.

As a result, fibers are no longer pinned to one thread. Even with parallelism 1, fibers may switch threads. The only guarantee is that no more than one fiber runs at any time. Code that relies on thread-local state across fiber yields should be reviewed.

The concrete breaking changes are:

Fibers in parallel execution contexts can resume in a different thread.
Fibers in concurrent execution contexts can switch threads on a blocking syscall.
Execution contexts don’t support spawn(same_thread:). In a parallel execution context, same_thread: true raises at runtime.

See Releasing Execution Contexts: Breaking Changes for details.

This effort is part of the ongoing project to improve multi-threading support with the help of 84codes.

Thanks @ysbaddaden

RFC 0021 introduces %W, a string array literal that complements %w with escape sequences and interpolation, including splats (#16919).

%W[foo\ bar baz] # => ["foo bar", "baz"]

%W[foo #{"bar"} baz]            # => ["foo", "bar", "baz"]
%W[foo #{1 + 1} baz]            # => ["foo", "2", "baz"]
%W[foo #{"bar"}baz#{"bab"} qux] # => ["foo", "barbazbab", "qux"]
%W[foo _#{"bar"}_ baz]          # => ["foo", "_bar_", "baz"]
%W[foo #{"bar baz"} qux]        # => ["foo", "bar baz", "qux"]

%W[foo #{*%w[bar baz]} qux] # => ["foo", "bar", "baz", "qux"]

Thanks, @straight-shoota

TypeNode#all_methods complements #methods by including methods from a type’s ancestors in addition to methods defined directly on the type (#16902).

Thanks, @Blacksmoke16

Channel(T) implements Iterator(T). This allows channels to plug directly into iterator-based APIs and chaining patterns (#16916).
```
channel = Channel(Int32).new
spawn do
  3.times { |i| channel.send(i) }
  channel.close
end

channel.to_a # => [0, 1, 2]
```
Thanks, @jgaskins
HTTP::WebSocket#receive is a synchronous call that enables a request/response style loop with blocking reads (#16689). This can be easier to use than the callback-based #run loop.

Thanks, @jgaskins
The -Dwithout_main flag allows building a binary without a main function, for example to serve as a dynamic library (#17074).

Thanks, @kojix2
JSON::Field now supports nested root properties (#17016), making it easier to map deeply nested payloads to flat object properties.

Thanks, @tcoatswo
URI::Params::Field adds ignore:, ignore_serialize, and ignore_deserialize options (#17029).

Thanks, @trypsynth
Spec matchers #should and #should_not can be chained to write more expressive expectations (#17020).
```
value.should(be_a(String)).should_not be_empty
```
Thanks, @straight-shoota
Process::Status.[] is a portable and explicit constructor for process exit statuses (#17003).

Thanks, @straight-shoota
String#present? is a convenient predicate for intent-revealing checks in guards and validations (#16930).

Thanks, @Sija
UUID.v6 and UUID.v8 generators (#17010).

Thanks, @trypsynth
Using mmap to read ELF, Mach-O, and PE files as well as some DWARF sections reduces overhead for parsing debug info (#16939).

Thanks, @ysbaddaden

Socket#sendfile (and Crystal::EventLoop::Socket#sendfile) enables efficient file-to-socket transfer paths with fewer user-space copies (#16665).

File.open("foo/bar") do |file|
  socket.sendfile(file)
end

Thanks, @ysbaddaden

Branches in case expressions with multiple type expressions now split into separate restrictions for each type (#17072). case x; when Bar, Baz is now equivalent to if x.is_a?(Bar) elsif x.is_a?(Baz). Previously, it was equivalent to if x.is_a?(Bar | Baz). The latter can still be expressed as when Bar | Baz.

Thanks, @straight-shoota
Improved debug metadata for procs (#16830), constants and class vars (#16831), and LLDB collection formatters (#16832) for better inspection and clearer debugger output.

Thanks, @skuznetsov
ASTNode#inspect now prints an unambiguous representation of the syntax node and its properties, instead of folding into the source representation (#16699).

Thanks, @straight-shoota

OpenSSL 4.0 (#16839)

Thanks, @straight-shoota

Colorize.on_tty_only! is obsolete because its behaviour is the default since #15881 (#16859).
spawn(same_thread:) only makes sense for legacy -Dpreview_mt and is pointless for execution contexts (#17097). See Execution Contexts
IO::Memory.new(writeable:): the parameter has been renamed to writable (#16858).
The platform-specific Process::Status.new constructor is hidden to avoid accidental misuse (#16997). A portable constructor Process::Status.[] is available as replacement.

Thanks, @straight-shoota, @ysbaddaden

Since 1.16, we’ve split the historic single manpage crystal(1) into individual pages for each subcommand. Now we’ve removed the original manpage from the repository. Manpage consumers must use the split manpages now.

We only provide the adoc sources, and package build scripts need to generate the roff format themselves (requires asciidoctor).

Package maintainers who ship manpages should update to the new build instructions if they haven’t already.

Makefile: Build manpages for install target (#16991)

Thanks, @straight-shoota

Thanks

We have been able to do all of this thanks to the continued support of 84codes and every other sponsor. To maintain and increase the development pace, donations, and sponsorships are essential. OpenCollective is available for that.

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.20.3 is released!

2026-07-02T00:00:00+00:00

We are announcing a new Crystal release 1.20.3 with fixes for two security vulnerabilities in the YAML parsers. We recommend upgrading as soon as possible if your application processes YAML files from unknown origins.

See the release notes of 1.20.0 for all the changes introduced in Crystal 1.20.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 2 security fixes and 1 refactor since 1.20.2 by 1 contributor. We thank all the contributors for all the effort put into improving the language! ❤️

The YAML parsers use recursion to parse sequences and mappings but didn’t limit how deep they could be nested. A deeply nested YAML document could lead to stack overflows (#17107).

Add max_nesting to YAML::PullParser (#17107)

Thanks, @ysbaddaden

The YAML parsers were vulnerable to the billion laughs attack when expanding aliases, growing the document from 100 nodes to over 1 billion nodes for example. The parser had no issues parsing the document, but any attempt to walk the stack could walk the same nodes over and over, quickly slowing down applications.

Add alias vs anchor ratio check to YAML::PullParser (#17109)
Memoize anchor name in YAML::PullParser (#17108)

Thanks, @ysbaddaden

For more details, visit the full changelog.

Thanks

We have been able to do all of this thanks to the continued support of 84codes and every other sponsor. To maintain and increase the development pace, donations and sponsorships are essential. OpenCollective is available for that.

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.20.2 is released!

2026-05-15T00:00:00+00:00

We are announcing a new Crystal release 1.20.2 with a couple of regressions fixed.

See the release notes of 1.20.0 for all the changes introduced in Crystal 1.20.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 2 bug fixes since 1.20.1 by 1 contributor. We thank all the contributors for all the effort put into improving the language! ❤️

This patch release brings the regression fix for Range#sample (#16909) that could eventually lose randomness to the 1.20 release branch. This was previously released as a backport for 1.19 in Crystal 1.19.2 (#16853).

Thanks, @ysbaddaden

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.20.1 is released!

2026-04-29T00:00:00+00:00

We are announcing a new Crystal release 1.20.1 with a couple of regressions fixed.

See the release notes of 1.20.0 for all the changes introduced in Crystal 1.20.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 9 changes since 1.20.0 by 2 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

Support for Kernel TLS was introduced in 1.20.0 but it showed issues in production. Some have been fixed (#16888) but there are still some problems so it was disabled by default (#16897).

You can opt-in to Kernel TLS by adding the ENABLE_KTLS option:

ssl_context.add_options(OpenSSL::SSL::Options::ENABLE_KTLS)

Thanks, @ysbaddaden

This patch release fixes a regression in Range#sample (#16853) that could eventually lose randomness.

Thanks, @ysbaddaden

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.19.2 is released!

2026-04-27T00:00:00+00:00

We are announcing a new Crystal release 1.19.2 with two regressions fixed.

See the release notes of 1.19.0 for all the changes introduced in Crystal 1.19.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 3 changes since 1.19.1 by 2 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

HTTP::Server accepted requests containing both Content-Length and Transfer-Encoding headers and prioritized Content-Length. This allowed HTTP request smuggling as per CWE-444 when the server is behind a vulnerable frontend. Refer to the advisory for more details.

HTTP::Server now rejects requests where both headers are present. The HTTP parser now ignores Content-Length when the Transfer-Encoding header is present (commit c948b31).

This patch release fixes a regression in Range#sample (#16866) that could eventually lose randomness.

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.20.0 is released!

2026-04-16T00:00:00+00:00

We are announcing a new Crystal release 1.20.0 with several new features and bug fixes.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 161 changes since 1.19.1 by 21 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

Below we list the most remarkable changes in the language, compiler and stdlib. For more details, visit the full changelog.

We do not expect any breaking changes in existing code. We expect the few bugfixes below to not negatively impact your programs. If you notice any unexpected issues, please let us know in the issue tracker or forum.

OpenSSL sockets shouldn’t flush on read (#16650)
Fix Process#wait to not close @input before waiting (#16620, #16638)
Ensure that heredoc lexing allows only valid identifiers (#16548)

Thanks @straight-shoota, @ysbaddaden, @Sija

HTTP::Server now rejects requests where both headers are present. The HTTP parser now ignores Content-Length when the Transfer-Encoding header is present. (commit c948b31).

RFC 0020 introduces a new @[TargetFeature] annotation that allows specifying CPU features or a CPU model or variant for individual functions. It complements the --mattr and --mcpu CLI arguments that target the whole program. This allows embedding multiple optimized functions for different CPU features into a single executable, for example a portable SIMD implementation alongside AVX2 and AVX512 alternatives.

The program is responsible for detecting which feature is available and calling the proper function at runtime. Otherwise, the program might crash with SIGILL, for example.

For example:

{% if flag?(:x86_64) %}
  @[TargetFeature("+avx2")]
  private def foo_avx2
  end

  private def cpu_supports_avx2?
  end
{% end %}

private def foo_portable
end

def foo
  {% if flag?(:x86_64) %}
    return foo_avx2 if cpu_supports_avx2?
  {% end %}
  foo_portable
end

While not strictly required, we still recommend wrapping architecture-specific method definitions within macro flag checks.

Add @[TargetFeature] annotation (#16717)

Thanks @stakach

Execution contexts from RFC 0002 continue as a final preview feature, enabled with the compiler flags -Dpreview_mt -Dexecution_context. We plan to enable it by default in Crystal 1.21.

In addition to fixing bugs, we implemented M:N scheduling that allows threads to be attached to and detached from a context. This avoids blocking other fibers on certain syscalls, such as getaddrinfo.

Add Fiber::ExecutionContext::ThreadPool (#15885, #16750)
Detach execution context scheduler from running thread during blocking syscall (#15871, #16679)

The parallel contexts now automatically start threads to adapt to the actual workload and distribute fibers across more cores when needed.

Add adaptive scaling to ExecutionContext::Parallel (#16719)

This effort is part of the ongoing project to improve multi-threading support with the help of 84codes.

Thanks @ysbaddaden

This release brings a new ergonomic, safe, and portable API for spawning sub-processes, as proposed in RFC 0025.

A significant change is that the modern API treats the command line as an array of strings. The first element is the program to execute, and the remaining elements are its arguments.

# legacy API:
Process.run("crystal", ["tool", "format"])

# modern API:
Process.run(["crystal", "tool", "format"])

The new API also includes convenient methods for capturing process output: Process.capture and Process.capture_result.

The new API does not have a shell parameter. If you need shell behaviour, we recommend running a shell explicitly.

These are the most significant individual changes:

Add overloads with combined args parameter instead of command, args (#16681, #16739)
Add Process.run? (#16738)
Add Process.capture (#16773)

All new methods and overloads are experimental. We expect to stabilize the API for the next release.

Thanks @straight-shoota

An io_uring event loop is available for Linux targets and can be selected by specifying -Devloop=io_uring when compiling. The event loop is highly experimental and its performance benefits will differ for every program. We don’t expect it to be faster than epoll, and it may even be slower, except on some benchmarks with SQPOLL enabled.

SQPOLL can be selected by specifying the idle time for the kernel threads with -Dio_uring_sq_thread_idle=200 (for 200ms). It is recommended to keep the idle time low (below 2s), otherwise your CPU cores will regularly spin at 100% usage when doing nothing.

An interesting but potentially surprising behavior is that any I/O call that could yield the calling fiber will now always yield. One benefit is that an always ready socket won’t block other fibers from progressing. A downside is that there might be lots of context switches.

Add io_uring event loop (linux) (#16264)

Thanks @ysbaddaden

Note

Kernel TLS is opt-in since 1.20.1 due to unresolved issues.

Kernel TLS is now supported by default on Linux and FreeBSD as long as support has been compiled into OpenSSL (which should be the default) and enabled on the system (likely disabled by default), for example with modprobe tls on Linux.

Add Kernel TLS support to custom OpenSSL::BIO (#16646)

Thanks @ysbaddaden

Add #select and #reject to HashLiteral and NamedTupleLiteral (#16558)
Refine error message for unsupported named arguments in macros (#16576)

Thanks @Blacksmoke16, @hahwul

OptionParser now supports option bundling and can parse -ncfoo as -n -c foo.

Add short option bundling for OptionParser (#16770)

Thanks @Qard

The OAuth module expected a success response on HTTP OK statuses, but multiple OAuth providers send error responses with an HTTP OK status (sic).

Detect OAuth error in payload (#16634)

Thanks @jgaskins

HTTP::WebSocket can now negotiate sub-protocols.

Add Sec-WebSocket-Protocol checks to HTTP::WebSocket::Protocol (#16600, #16671)
Add support for Sec-WebSocket-Protocol to HTTP::WebSocketHandler (#16574)

Thanks @antondalgren, @straight-shoota

StringScanner saw multiple improvements, ranging from performance to subtle niceties for debugging.

Add StringScanner#scan, #check, and #skip overloads for Int (#16557)
Add StringScanner#peek_behind (#16593)
Add convenience methods to StringScanner (#16595)
Improve cursor window format in StringScanner#inspect (#16594)

Thanks @jneen

The memory management model for libxml2 changed in Crystal 1.17 to become manual instead of integrating the GC. The change introduced another memory leak that is now fixed.

Call xmlFree for the string pointer from xmlNodeGetContent (#16688)

Thanks @toddsundsted

Some additional niceties:

Add IO#read_greedy (#16535)
Add FileUtils#rm_f (#12832)
Add Pointer#align_up and #align_down (#16585)
Add HTTP::Server::Response#content_type and #content_length as convenient accessors (#16712)

Thanks @BlobCodes, @CTC97, @zw963

Prefer modern linker (mold or lld) (#16696)

Thanks @straight-shoota

Parse MacroVar with empty expressions: %var{} (#16772)
Parse ProcNotation with empty arg parenthesis: () -> (#16741)
Add --base-path for crystal docs (#16091)

Thanks @straight-shoota, @matiasgarciaisaia

Support for LLVM 22.1 and 23.0 (#16631)

Thanks @HertzDevil

There is a single deprecation in this release, and it is a trivial one: rename Mutex to Sync::Mutex to use the new algorithm introduced in Crystal 1.19.

We’re experimenting with a two-step mechanism to deprecate a feature. First, we soft deprecate the method in the documentation with a DEPRECATE: callout, then after a few releases we’ll hard deprecate by adding the @[Deprecated] annotation.

Soft deprecate Mutex in favor of Sync::Mutex (#16737)

Thanks @ysbaddaden

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.19.1 is released!

2026-01-20T00:00:00+00:00

We are announcing a new Crystal release 1.19.1 with two regressions fixed.

See the release notes of 1.19.0 for all the changes introduced in Crystal 1.19.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 2 changes since 1.19.0 by 1 contributor. We thank all the contributors for all the effort put into improving the language! ❤️

This patch release fixes regressions in timer conversions from absolute to relative time (#16581, #16583) that led sleep(seconds) to immediately trigger instead of waiting on some platforms (Darwin, BSDs, Windows) — both introduced in 1.19.0.

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.19.0 is released!

2026-01-15T00:00:00+00:00

We are announcing a new Crystal release 1.19.0 with several new features and bug fixes.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 237 changes since 1.18.2 by 24 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

Below we list the most remarkable changes in the language, compiler and stdlib. For more details, visit the full changelog.

We do not expect any breaking changes in existing code. If you notice any unexpected issues, please let us know in the issue tracker or forum.

The following changes break prior behavior of the compiler, but we expect them to not have much effect in existing code. If you notice any unexpected issues, please let us know in the issue tracker or forum.

The flag? macro is now aware of name-value mappings in the form of name=value where flag?(:name) will now return the respective value as a StringLiteral (#16310). A key without a value returns true as implicit value, as before.

Instead of returning a BoolLiteral the flag? macro might now return a StringLiteral which might be unexpected. The value is still truthy and shouldn’t cause issues in practice.

For example, the value printed by {{ flag?(:name) }} may now be:

(not defined) => false
-Dname => true
-Dname=value => "value"
-Dname=some,other,data => "some,other,data"

Thanks, @straight-shoota

The monotonic clock has been adjusted on Linux and macOS to include suspended time, when they previously counted the system uptime.

UNIX targets still use CLOCK_MONOTONIC except for Linux that now uses CLOCK_BOOTTIME (#16516) and macOS that now uses CLOCK_MONOTONIC_RAW instead of mach_absolute_time that internally used CLOCK_UPTIME_RAW (#16516, #16492).

The change is affecting Time.measure for example, that should now include suspended time across the different targets, rather than sometimes including it, and sometimes not.

Execution contexts from RFC 0002 continue as a final preview feature with opt-in with compiler flags -Dpreview_mt -Dexecution_context and we plan to finally enable the feature by default in the 1.20 release!

There has not been huge developments to the feature, but corrections to fix the remaining thread safety issues in the standard library, for example:

Add thread safety to default random (#16174)
Closing system fd is thread unsafe (#16289)
Thread safety of Exception::Callstack (#16504)

We started to merge synchronization primitives from ysbaddaden/sync into the standard library as well:

Add Sync::Mutex and Sync::RWLock (#16399)
Add Sync::ConditionVariable (#16440)
Add Sync::Exclusive and Sync::Shared (#16487)

This effort is part of the ongoing project to improve multi-threading support with the help of 84codes.

Thanks, @ysbaddaden

Introduces the Time::Instant type to represent instants on the monotonic timeline as defined in RFC 0015 instead of overloading the Time::Span type that represents a duration, not an instant (#16490). We expect a clearer and safer API:

Time::Instant represents a single point on the monotonic timeline.
Time::Span continues to represent a duration.
Subtracting two Time::Instant instances yields a Time::Span.
Adding/subtracting a Time::Span to/from an Time::Instant yields a new Time::Instant.

We also adjusted the monotonic clock (#16516), applied the changes (#16498) and deprecated Time.monotonic (#16545).

For example:

timeout = 5.seconds
start = Time.instant

while start.elapsed < timeout
  # do something
end

In order to migrate existing code to Time::Instant, replace calls to Time.monotonic with Time.instant. If the instant time reading is stored in an explicitly typed variable (e.g. an instance variable), change the type from Time::Span to Time::Instant. The APIs of these types are very similar so most use cases should not need any further adaptions.

Finally, we made some further adjustments:

Treat GMT as a legacy alias of UTC (#16292)
Add /etc/zoneinfo to zoneinfo lookup paths (#16463)
Add support for $TZDIR (#16466)

Thanks, @straight-shoota

A long refactor of spawning sub-processes has started. It encompasses a tedious cleanup and safety fixes related to finding the command as well as building the arguments and environment variables, to eventually move on from the classic fork then exec to the more modern posix_spawn on UNIX targets.

Process.run and Process.exec now look up the target executable in the environment of the parent process (ENV["PATH"]) instead of in the environment of the child process (env["PATH"]) on all platforms (#16340). This is usually the expected and specified behaviour for spawning a new process, but it only worked correctly on Windows until now. Consider using a full path (possibly resolved via Process.find_executable) if you want to look up the executable in a different path. With shell: true, the target executable is also looked up in env["PATH"] because the shell process sits in between.

Create argv before fork (#16286, #16321)
Move make_envp before fork (#16351)
Use execvpe when available (#16294, #16311)
Replace Dir.cd with a non-raising alternative in pre-exec (#16352, #16369)
Fix reset directory if Process.exec fails (#16383)
Disable process cancellation during fork (#16446)

Thanks, @straight-shoota

New methods:

Add NamedTuple#reverse_merge (#16229)
Add Set#map! (#16271)
Add Hash#transform_keys! (#16280)
Add OpenSSL::SSL::Context::Server#on_server_name for SNI (#16452, #16525)
Add IPSocket#ipv6_only (#16347)
Add Int.from_digits as inverse of Int#digits (#16237)
Add BigInt.from_digits (#16259)
Add Int#tdivmod (#16258)
Add Random.next_bool and Random.next_int (#16297)
Add Random#split and Random.split for splittable PRNGs (#16342, #16495)
Add Pointer#fill (#16338)
Add Process.debugger_present? for Windows and Linux (#16248)
Add Path#relative? (#16473)
Add YAML::Nodes.parse_all (#16247)
Add ::exit(Process::Status) (#16436)

Enhancements:

Support large JSON files (#16211)
Support deserialization of YAML anchors of value types (#16186)
Add end locations to scalars and aliases in YAML::Nodes.parse (#16187)
Set JSON::SerializableError#attribute when appropriate (#16158)
Add remove_empty parameter to String#each_line (#16232)
Add weeks parameter to Time::Span.new (#16208)
Support 0X, 0O, 0B prefixes in string to integer conversion (#16226)

Thanks, @andrykonchin, @carlhoerberg, @HertzDevil, @ysbaddaden, @straight-shoota, @RX14, @Sija, @spuun

The memory management model for libxml2 changed in Crystal 1.17 to become manual instead of integrating the GC. The change introduced some memory leaks that have now been fixed.

Memory leak in XML.parse and XML.parse_html methods (#16414)
Memory leak in XML::Document#finalize (#16418)
Memory leak in XML::Node#content= (#16419)
Fix use after unlink in XML::Node (#16432)

Thanks, @toddsundsted

New methods:

Thanks, @Blacksmoke16, @HertzDevil

All overloads of ArrayLiteral#[] return nil on out of bounds (#16453)

Thanks, @HertzDevil

The compiler is now always built with execution contexts, and the LLVM codegen is now always multithreaded for every target, including Windows. We can finally wave goodbye to fork, and Windows should see a performance boost.

Tools:

Add optional sanitizer to docs generator (#14646, #16251)

Thanks [@nobodywasishere], @straight-shoota

We finally build Linux ARM64 binaries of Crystal releases and nightlies. Tarballs are ready to download from GitHub releases, docker images, snapcraft or the install-crystal GitHub action.

Build linux aarch64 tarballs (#16330)
Build snap arm64 target (#16491)
Enable multiarch docker builds (#16493)
Encourage +1 reactions on issues and PRs for prioritization (#16241)

Thanks @straight-shoota, @ysbaddaden

The OpenSSL bindings now require OpenSSL 1.1.1+ or LibreSSL 3+. We expect the change to not have any effect since these versions are no longer distributed by any supported operating system.

Thanks @ysbaddaden

Deprecate single-letter macro fresh variables with indices (#16267)
Deprecate macro fresh variables with constant names (#16293)
Deprecate StringLiteral#split(ASTNode) (#16439)
Deprecate Time.monotonic (#16545)
Deprecate Time#inspect(io, *, with_nanoseconds) (#16416)

Thanks @HertzDevil, @straight-shoota

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.18.2 is released!

2025-10-21T00:00:00+00:00

We are announcing a new Crystal release 1.18.2 with two regressions fixed.

See the release notes of 1.18.0 for all the changes introduced in Crystal 1.18.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 3 changes since 1.18.1 by 3 contributors. We thank all the contributors for all the effort put into improving the language! ❤️

This patch release fixes a regression in the type restrictions of IO#read_bytes (#16231), and a bug in Fiber::ExecutionContext.default_workers_count (#16227) - both errors were introduced in 1.18.0.

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal 1.18.1 is released!

2025-10-17T00:00:00+00:00

We are announcing a new Crystal release 1.18.1 with two regressions fixed.

See the release notes of 1.18.0 for all the changes introduced in Crystal 1.18.

Pre-built packages are available on GitHub Releases and our official distribution channels. See crystal-lang.org/install for installation instructions.

This release includes 2 changes since 1.18.0 by 1 contributor. We thank all the contributors for all the effort put into improving the language! ❤️

This patch release fixes a regression in the enum def parsing (#16217), and overly strict type restrictions in HTTP::WebSocket (#16218) - both introduced in 1.18.0.

For more details, visit the full changelog.

Thanks

Reach out to crystal@manas.tech if you’d like to become a direct sponsor or find other ways to support Crystal. We thank you in advance!

Contribute

Crystal Releases

Crystal 1.21.0 is released!

Stats

Changes

Breaking

Execution contexts

Percent string array literal with interpolation

Macros

Standard library

Experimental: Socket#sendfile

Compiler

Dependencies

Deprecations

Manpages

Crystal 1.20.3 is released!

Stats

Changes

Limit max nesting of sequences of mappings in YAML parsers

Prevent excessive expansion of aliases in YAML parsers

Crystal 1.20.2 is released!

Stats

Changes

Randomness in Range#sample

Crystal 1.20.1 is released!

Stats

Changes

Kernel TLS

Randomness in Range#sample

Crystal 1.19.2 is released!

Stats

Changes

Security

Regressions

Crystal 1.20.0 is released!

Stats

Changes

Breaking

Security

Target features

Execution contexts

Process API

io_uring

Kernel TLS

Macros

Standard library

Compiler

Dependencies

Deprecations

Crystal 1.19.1 is released!

Stats

Changes

Crystal 1.19.0 is released!

Stats

Changes

Breaking

Compiler flags now have values

Adjust monotonic clocks

Execution contexts

Time

Process

Standard library

Macros

Compiler

Infra

Dependencies

Deprecations

Crystal 1.18.2 is released!

Stats

Changes

Crystal 1.18.1 is released!

Stats

Changes

Experimental: `Socket#sendfile`

Randomness in `Range#sample`

Randomness in `Range#sample`