Skip to content

Release 0.4.0 - #7

Merged
igray merged 1 commit into
mainfrom
release-0.4.0
Aug 1, 2026
Merged

Release 0.4.0#7
igray merged 1 commit into
mainfrom
release-0.4.0

Conversation

@igray

@igray igray commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Version bump for the release following #6.

Why 0.4.0 and not 0.3.2

#6 narrowed the ruby-lsp dependency from ~> 0.17, >= 0.12.0 to ~> 0.26, dropping support for nine minor versions of the host LSP. Anyone pinned to ruby-lsp 0.17–0.25 cannot take this upgrade. On a 0.x gem the minor slot is where breaking changes go, so a patch bump would misrepresent it.

Two smaller compatibility notes, neither of which drives the decision on its own:

  • required_ruby_version went >= 2.5.0>= 3.0.0. This is mostly a correction rather than a real narrowing — ruby-lsp 0.17 already required Ruby >= 3.0, so 2.5 was never actually viable. It is now enforced at install time.
  • sorbet-runtime is no longer a dependency. Not a break for this gem's own API, but anyone who was implicitly relying on ruby-lsp-reek to pull sorbet-runtime into their bundle will no longer get it.

The two methods removed from Runner (build_examiner, warning_to_diagnostic) were both private, so they are not part of the public surface.

Verification

Built the 0.4.0 gem and inspected the artifact:

version: 0.4.0
ruby: >= 3.0.0
runtime: reek ~> 6.0
runtime: ruby-lsp ~> 0.26
files: lib/ruby_lsp/reek/addon.rb, lib/ruby_lsp/reek/diagnostic.rb,
       lib/ruby_lsp/reek/runner.rb, lib/ruby_lsp/reek/version.rb

No sorbet-runtime, and diagnostic.rb is packaged. Suite is green: 4 runs, 14 assertions, 0 failures, and rake code_analysis reports 0 total warnings.

🤖 Generated with Claude Code

Bump to 0.4.0 rather than 0.3.2. The ruby-lsp upgrade in #6 narrowed the
dependency from `~> 0.17, >= 0.12.0` to `~> 0.26`, so anyone pinned to
ruby-lsp 0.17 through 0.25 cannot take this upgrade. On a 0.x gem the minor
slot is where breaking changes go.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@igray
igray merged commit f132362 into main Aug 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant