ruby-next 1.0.3 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e404053f4c0ea48bfed4dca7cd28446c912b3371f2a318dae6da890ff0764be4
-  data.tar.gz: 4f520ce514d2a4d1b9ec5491e3d47fedf821ecb0841038e4f49b96f44ea7ddfd
+  metadata.gz: 8d02021cba138ffde5ada984fd1d3848a6fe666128bf9f61ae8fd4d16ea3e762
+  data.tar.gz: c9b212735494e26f9ccfe759e5cd039f1d8217e705b97fcde118698ab43d97a3
 SHA512:
-  metadata.gz: 17e38527a8ba3423c0c7f0605d0bdf76e32fbbed8c95608b1af708bba5ed00f8292d5e863a6a96af05a73e3217b168ce6c2508be033e52e6caeb0f0847962f29
-  data.tar.gz: 71b6e39a4b334728d96c5f62170bd80675475d10280b200da743dde105473ea52571c41a8e52504ac80065ec0e24e69b5a999d53601750736cec5d51ac3e750b
+  metadata.gz: a4e958626a9c250e4425a64a233bd9923035421046241a34b293118716e9c4e5704173b4cb258b213e3010ebdae6796b262bc0346a33dc63d1a45838c6e76897
+  data.tar.gz: 4c4969d33ccee6113a0d4e1a2c5eb7e3392340479e836fb2970e651b1dad1a91eecaafef11950a7f063f6c1fba0c1c4419734d6e0079dc9e3e5f6564ea942194

data/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## master
 
+## 1.1.0 (2025-01-15)
+
+- Prepare for Ruby 3.5.
+
 ## 1.0.3 (2024-04-18)
 
 - Fix RuboCop compatibility.

data/README.md

@@ -364,6 +364,20 @@ If the command fails we warn the end user.
 
 This feature, _auto-transpiling_, is **disabled** by default (will likely be enabled in future versions). You can enable it by calling `RubyNext::Language.setup_gem_load_path(transpile: true)`.
 
+### Dependency-less setup
+
+If you want to avoid adding `ruby-next-core` to your gem's dependencies, you can tweak the `$LOAD_PATH` yourself. It's much easier to do if you go with a single transpiled version per source file (i.e., use `--single-version` or specify particular rewriters using the `--rewrite` option of the `ruby-next nextify` command). If so, you can drop the following snippet to your gem's entrypoint:
+
+```ruby
+# lib/my_gem.rb
+$LOAD_PATH.unshift "#{__dir__}/.rbnext"
+
+# Then go `require` statements
+# ...
+```
+
+That's it! Keep in mind that in this cases there is no auto-transpiling support (so, you may want to keep the transpiled files in the repository to allow installing the gem from source).
+
 ## Runtime usage
 
 It is also possible to transpile Ruby source code in run-time via Ruby Next.
@@ -552,7 +566,7 @@ require "ruby-next/language/runtime"
 
 ### Supported edge features
 
-- Implicit `it` block parameter ([#19890](https://bugs.ruby-lang.org/issues/18980)).
+None yet.
 
 ### Supported proposed features
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-next
 version: !ruby/object:Gem::Version
-  version: 1.0.3
+  version: 1.1.0
 platform: ruby
 authors:
 - Vladimir Dementyev
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-04-18 00:00:00.000000000 Z
+date: 2025-01-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ruby-next-core
@@ -16,28 +16,28 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 1.0.3
+        version: 1.1.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 1.0.3
+        version: 1.1.0
 - !ruby/object:Gem::Dependency
   name: ruby-next-parser
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.2.2.0
+        version: 3.4.0.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.2.2.0
+        version: 3.4.0.2
 - !ruby/object:Gem::Dependency
   name: require-hooks
   requirement: !ruby/object:Gem::Requirement