acfs 2.1.0 → 2.2.1

data/vendor/bundle/ruby/{3.4.0/gems/ffi-1.17.1-x86_64-linux-gnu → 4.0.0/gems/ffi-1.17.4-x86_64-linux-gnu}/README.md

@@ -33,6 +33,7 @@ MyLib.puts 'Hello, World using libc!'
 
 For less minimalistic and more examples you may look at:
 
+* The [documentation](https://www.rubydoc.info/gems/ffi)
 * the `samples/` folder
 * the examples on the [wiki](https://github.com/ffi/ffi/wiki)
 * the projects using FFI listed on the wiki: https://github.com/ffi/ffi/wiki/projects-using-ffi

data/vendor/bundle/ruby/{3.4.0/gems/ffi-1.17.1-x86_64-linux-gnu → 4.0.0/gems/ffi-1.17.4-x86_64-linux-gnu}/ffi.gemspec

@@ -15,13 +15,16 @@ Gem::Specification.new do |s|
     s.metadata['wiki_uri'] = 'https://github.com/ffi/ffi/wiki'
     s.metadata['source_code_uri'] = 'https://github.com/ffi/ffi/'
     s.metadata['mailing_list_uri'] = 'http://groups.google.com/group/ruby-ffi'
+    s.metadata['rubygems_mfa_required'] = 'true'
   end
   s.files = `git ls-files -z`.split("\x0").reject do |f|
-    f =~ /^(\.|bench|gen|libtest|nbproject|spec)/
+    f =~ /^(\.|bench|gen|libtest|nbproject|spec|rakelib)/
   end
 
   # Add libffi git files
-  lfs = `git --git-dir ext/ffi_c/libffi/.git ls-files -z`.split("\x0")
+  lfs = `git --git-dir ext/ffi_c/libffi/.git ls-files -z`.split("\x0").reject do |f|
+    f =~ /^(\.|testsuite)/
+  end
   # Add autoconf generated files of libffi
   lfs += %w[ compile configure config.guess config.sub install-sh ltmain.sh missing fficonfig.h.in ]
   # Add automake generated files of libffi
@@ -35,8 +38,6 @@ Gem::Specification.new do |s|
   s.license = 'BSD-3-Clause'
   s.require_paths << 'ext/ffi_c'
   s.required_ruby_version = '>= 2.5'
-  s.add_development_dependency 'rake', '~> 13.0'
-  s.add_development_dependency 'rake-compiler', '~> 1.1'
-  s.add_development_dependency 'rake-compiler-dock', '~> 1.0'
-  s.add_development_dependency 'rspec', '~> 2.14.1'
+
+  s.metadata['msys2_mingw_dependencies'] = 'libffi'
 end

data/vendor/bundle/ruby/{3.4.0/gems/hashdiff-1.1.2 → 4.0.0/gems/hashdiff-1.2.1}/README.md

@@ -95,7 +95,8 @@ Hashdiff.unpatch!(b, diff).should == a
 ### Options
 
 The following options are available: `:delimiter`, `:similarity`, `:strict`, `:ignore_keys`,
-`:indifferent`, `:numeric_tolerance`, `:strip`, `:case_insensitive`, `:array_path` and `:use_lcs`
+`:indifferent`, `:numeric_tolerance`, `:strip`, `:case_insensitive`, `:array_path`, 
+`:use_lcs`, and `:preserve_key_order`
 
 #### `:delimiter`
 
@@ -235,6 +236,30 @@ diff = Hashdiff.diff(a, b, use_lcs: false)
 diff.should == [["~", "x[1]", 1, 2], ["+", "x[3]", 3]]
 ```
 
+#### `:preserve_key_order`
+
+By default, the change set is ordered by operation type: deletions (-) first, then updates (~), and finally additions (+). 
+Within each operation group, keys are sorted alphabetically:
+
+```ruby
+a = {d: 1, c: 1,       a: 1}
+b = {d: 2,       b: 2, a: 2}
+
+diff = Hashdiff.diff(a, b)
+diff.should == [["-", "c", 1], ["~", "a", 1, 2], ["~", "d", 1, 2], ["+", "b", 2]]
+```
+
+Setting :preserve_key_order to true processes keys in the order they appear in the first hash.
+Keys that only exist in the second hash are appended in their original order:
+
+```ruby
+a = {d: 1, c: 1,       a: 1}
+b = {d: 2,       b: 2, a: 2}
+
+diff = Hashdiff.diff(a, b, preserve_key_order: true)
+diff.should == [["~", "d", 1, 2], ["-", "c", 1], ["~", "a", 1, 2], ["+", "b", 2]]
+```
+
 #### Specifying a custom comparison method
 
 It's possible to specify how the values of a key should be compared.

data/vendor/bundle/ruby/4.0.0/gems/hashdiff-1.2.1/changelog.md

@@ -0,0 +1,127 @@
+# Change Log
+
+## v1.2.1 2025-09-06
+
+* Use HTTPS for the source in the Gemfile [#101](https://github.com/liufengyun/hashdiff/issues/101) ([@krzysiek1507](https://github.com/krzysiek1507))
+
+## v1.2.0 2025-5-20
+
+* Added :preserve_key_order option to maintain original hash key order [#99](https://github.com/liufengyun/hashdiff/issues/99) ([@robkiessling](https://github.com/robkiessling))
+
+## v1.1.2 2024-11-12
+
+* Fix bundler cache [#96](https://github.com/liufengyun/hashdiff/issues/96) ([@olleolleolle](https://github.com/olleolleolle))
+* Quote the '3.0' in YAML [#95](https://github.com/liufengyun/hashdiff/issues/95) ([@olleolleolle](https://github.com/olleolleolle))
+* Fix version in source code [#97](https://github.com/liufengyun/hashdiff/issues/97) ([@liufengyun](https://github.com/liufengyun))
+
+## v1.1.1 2024-08-02
+
+* Fix bug in ignore_keys option [#88](https://github.com/liufengyun/hashdiff/issues/88) ([@Matzfan](https://github.com/Matzfan))
+* Exclude spec files from gem package [#94](https://github.com/liufengyun/hashdiff/issues/94) ([@amatsuda](https://github.com/amatsuda))
+
+## v1.1.0 2023-12-14
+
+* Add ignore_keys option ([#86](https://github.com/liufengyun/hashdiff/issues/86) [@Matzfan](https://github.com/Matzfan))
+* Remove pinned version of rake < 11
+* Bump rspec dep ~> 3.5
+* Bump rubocop dep >= 1.52.1
+* Bump rubocop-rspec dep > 1.16.0
+
+## v1.0.1 2020-02-25
+
+* Add indifferent option
+
+## v1.0.0 2019-06-06
+
+* Fix typo in readme ([#72](https://github.com/liufengyun/hashdiff/issues/72) [@koic](https://github.com/koic))
+* Fix Rubocop offence ([#73](https://github.com/liufengyun/hashdiff/issues/73) [@koic](https://github.com/koic))
+* Bumps version to v1.0.0 ([#74](https://github.com/liufengyun/hashdiff/issues/74) [@jfelchner](https://github.com/jfelchner))
+
+## v1.0.0.beta1 2019-06-06
+
+* fix warnings in ci ([#69](https://github.com/liufengyun/hashdiff/issues/69) [@y-yagi](https://github.com/y-yagi))
+* drop warnings of the constant change ([#70](https://github.com/liufengyun/hashdiff/issues/70) [@jfelchner](https://github.com/jfelchner))
+
+## v0.4.0 2019-05-28
+
+* refactoring ([#56](https://github.com/liufengyun/hashdiff/issues/56) [#57](https://github.com/liufengyun/hashdiff/issues/57) [#59](https://github.com/liufengyun/hashdiff/issues/59) [#61](https://github.com/liufengyun/hashdiff/issues/61) [@krzysiek1507](https://github.com/krzysiek1507))
+* fix typo in README ([#64](https://github.com/liufengyun/hashdiff/issues/64) [@pboling](https://github.com/pboling))
+* change HashDiff to Hashdiff ([#65](https://github.com/liufengyun/hashdiff/issues/65) [@jfelchner](https://github.com/jfelchner))
+
+## v0.3.9 2019-04-22
+
+* Performance tweak (thanks [@krzysiek1507](https://github.com/krzysiek1507): [#51](https://github.com/liufengyun/hashdiff/issues/51) [#52](https://github.com/liufengyun/hashdiff/issues/52) [#53](https://github.com/liufengyun/hashdiff/issues/53))
+
+## v0.3.8 2018-12-30
+
+* Add Rubocop and drops Ruby 1.9 support [#47](https://github.com/liufengyun/hashdiff/issues/47)
+
+## v0.3.7 2017-10-08
+
+* remove 1.8.7 support from gemspec [#39](https://github.com/liufengyun/hashdiff/issues/39)
+
+## v0.3.6 2017-08-22
+
+* add option `use_lcs` [#35](https://github.com/liufengyun/hashdiff/issues/35)
+
+## v0.3.5 2017-08-06
+
+* add option `array_path` [#34](https://github.com/liufengyun/hashdiff/issues/34)
+
+## v0.3.4 2017-05-01
+
+* performance improvement of `#similar?` [#31](https://github.com/liufengyun/hashdiff/issues/31)
+
+## v0.3.2 2016-12-27
+
+* replace `Fixnum` by `Integer` [#28](https://github.com/liufengyun/hashdiff/issues/28)
+
+## v0.3.1 2016-11-24
+
+* fix an error when a hash has mixed types [#26](https://github.com/liufengyun/hashdiff/issues/26)
+
+## v0.3.0 2016-2-11
+
+* support `:case_insensitive` option
+
+## v0.2.3 2015-11-5
+
+* improve performance of LCS algorithm [#12](https://github.com/liufengyun/hashdiff/issues/12)
+
+## v0.2.2 2014-10-6
+
+* make library 1.8.7 compatible
+
+## v0.2.1 2014-7-13
+
+* yield added/deleted keys for custom comparison
+
+## v0.2.0 2014-3-29
+
+* support custom comparison blocks
+* support `:strip`, `:numeric_tolerance` and `:strict` options
+
+## v0.1.0 2013-8-25
+
+* use options for parameters `:delimiter` and `:similarity` in interfaces
+
+## v0.0.6 2013-3-2
+
+* Add parameter for custom property-path delimiter.
+
+## v0.0.5 2012-7-1
+
+* fix a bug in judging whehter two objects are similiar.
+* add more spec test for `.best_diff`
+
+## v0.0.4 2012-6-24
+
+Main changes in this version is to output the whole object in addition & deletion, instead of recursely add/deletes the object.
+
+For example, `diff({a:2, c:[4, 5]}, {a:2}) will generate following output:
+
+    [['-', 'c', [4, 5]]]
+
+instead of following:
+
+    [['-', 'c[0]', 4], ['-', 'c[1]', 5], ['-', 'c', []]]

data/vendor/bundle/ruby/{3.4.0/gems/i18n-1.14.7 → 4.0.0/gems/i18n-1.15.2}/README.md

@@ -19,7 +19,7 @@ We support Rails versions from 6.0 and up.
 
 ### Ruby (without Rails)
 
-We support Ruby versions from 3.0 and up.
+We support Ruby versions from 3.1 and up.
 
 If you want to use this library without Rails, you can simply add `i18n` to your `Gemfile`:
 
@@ -54,6 +54,18 @@ I18n.locale = :de
 I18n.t(:test) # => "Dies ist ein Test"
 ```
 
+### Fiber-safe config updates
+
+`Fiber[]` values are inherited by child fibers.
+To avoid sharing mutable config objects across fibers, prefer creating updated configs and setting them with `set!`:
+
+```ruby
+I18n.config.with(locale: :ja).set!
+```
+
+`set!` stores a frozen config in the current execution context.
+This keeps inherited state safe and lets updates happen by replacing config objects.
+
 ## Features
 
 * Translation and localization

data/vendor/bundle/ruby/{3.4.0/gems/json-2.10.1 → 4.0.0/gems/json-2.19.9}/README.md

@@ -97,7 +97,7 @@ Instead it is recommended to use the newer `JSON::Coder` API:
 
 ```ruby
 module MyApp
-  API_JSON_CODER = JSON::Coder.new do |object|
+  API_JSON_CODER = JSON::Coder.new do |object, is_object_key|
     case object
     when Time
       object.iso8601(3)
@@ -113,6 +113,24 @@ puts MyApp::API_JSON_CODER.dump(Time.now.utc) # => "2025-01-21T08:41:44.286Z"
 The provided block is called for all objects that don't have a native JSON equivalent, and
 must return a Ruby object that has a native JSON equivalent.
 
+It is also called for objects that do have a JSON equivalent, but are used as Hash keys, for instance `{ 1 => 2}`,
+as well as for strings that aren't valid UTF-8:
+
+```ruby
+coder = JSON::Combining.new do |object, is_object_key|
+  case object
+  when String
+    if !string.valid_encoding? || string.encoding != Encoding::UTF_8
+      Base64.encode64(string)
+    else
+      string
+    end
+  else
+    object
+  end
+end
+```
+
 ## Combining JSON fragments
 
 To combine JSON fragments into a bigger JSON document, you can use `JSON::Fragment`:
@@ -231,8 +249,32 @@ There are also the methods `Kernel#j` for generate, and `Kernel#jj` for
 `pretty_generate` output to the console, that work analogous to Core Ruby's `p` and
 the `pp` library's `pp` methods.
 
+## Security
+
+When parsing or serializing untrusted input, parser and generator options should never be user controlled.
+
+```ruby
+# Dangerous, DO NOT DO THIS.
+JSON.generate(params[:data], params[:options])
+```
+
+Security vulnerability reports relying on attacker controlled parsing or generator options will be handled as regular bug fixes.
+
 ## Development
 
+### Prerequisites
+
+1. Clone the repository
+2. Install dependencies with `bundle install`
+
+### Testing
+
+The full test suite can be run with:
+
+```bash
+bundle exec rake test
+```
+
 ### Release
 
 Update the `lib/json/version.rb` file.

data/vendor/bundle/ruby/{3.4.0/gems/json-2.10.1 → 4.0.0/gems/json-2.19.9}/json.gemspec

@@ -44,15 +44,14 @@ spec = Gem::Specification.new do |s|
     "LEGAL",
     "README.md",
     "json.gemspec",
-    *Dir["lib/**/*.rb"],
-  ]
+  ] + Dir.glob("lib/**/*.rb", base: File.expand_path("..", __FILE__))
 
   if java_ext
     s.platform = 'java'
     s.files += Dir["lib/json/ext/**/*.jar"]
   else
     s.extensions = Dir["ext/json/**/extconf.rb"]
-    s.files += Dir["ext/json/**/*.{c,h}"]
+    s.files += Dir["ext/json/**/*.{c,h,rb}"]
   end
 end
 

data/vendor/bundle/ruby/4.0.0/gems/language_server-protocol-3.17.0.5/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Fumiaki MATSUSHIMA
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/vendor/bundle/ruby/4.0.0/gems/language_server-protocol-3.17.0.5/README.md

@@ -0,0 +1,88 @@
+# LanguageServer::Protocol
+
+A Language Server Protocol SDK for Ruby.
+
+[![Gem Version](https://badge.fury.io/rb/language_server-protocol.svg)](https://badge.fury.io/rb/language_server-protocol)
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'language_server-protocol'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install language_server-protocol
+
+## Usage
+
+Currently, this gem supports only stdio as transport layer out of box.
+
+```ruby
+require "language_server-protocol"
+
+LSP = LanguageServer::Protocol
+writer = LSP::Transport::Stdio::Writer.new
+reader = LSP::Transport::Stdio::Reader.new
+
+subscribers = {
+  initialize: -> {
+    LSP::Interface::InitializeResult.new(
+      capabilities: LSP::Interface::ServerCapabilities.new(
+        text_document_sync: LSP::Interface::TextDocumentSyncOptions.new(
+          change: LSP::Constant::TextDocumentSyncKind::FULL
+        ),
+        completion_provider: LSP::Interface::CompletionOptions.new(
+          resolve_provider: true,
+          trigger_characters: %w(.)
+        ),
+        definition_provider: true
+      )
+    )
+  }
+}
+
+reader.read do |request|
+  result = subscribers[request[:method].to_sym].call
+  writer.write(id: request[:id], result: result)
+  exit
+end
+```
+
+You can use any IO object as transport layer:
+
+```ruby
+io = StringIO.new
+writer = LSP::Transport::Io::Writer.new(io)
+reader = LSP::Transport::Io::Reader.new(io)
+```
+
+## Versioning
+
+language_server-protocol gem does NOT use semantic versioning.
+This gem versions are structured as `x.y.z.t`.
+`x.y.z` indicates the [Language server protocol](https://github.com/Microsoft/language-server-protocol/) version and `t` is a monotonically increasing number.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/mtsmfm/language_server-protocol-ruby. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the LanguageServer::Protocol project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/mtsmfm/language_server-protocol-ruby/blob/main/CODE_OF_CONDUCT.md).

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+## [Unreleased]
+
+## [1.1.0]
+
+- Add `LintRoller::Support` module of classes designed to make it a little
+easier to author plugins. `MergesUpstreamMetadata#merge` will allow a minimal
+YAML config (say, `standard-sorbet`'s, which only contains `Enabled` values for
+each rule) to merge in any other defaults from a source YAML (e.g.
+`rubocop-sorbet`'s which includes `Description`, `VersionAdded`, and so on).
+This way that metadata is neither absent at runtime nor duplicated in a standard
+plugin that mirrors a rubocop extension
+
+## [1.0.0]
+
+- Initial release

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 Test Double, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/README.md

@@ -0,0 +1,173 @@
+# lint_roller - A plugin specification for linters
+
+`lint_roller` is an itty-bitty plugin API for code analysis tools like linters
+and formatters. It provides plugins for those tools to load extensions and
+specify custom rulesets.
+
+(As of this release, only [Standard
+Ruby](https://github.com/standardrb/standard) supports `lint_roller` plugins,
+but we think [RuboCop](https://github.com/rubocop/rubocop) could add support and
+most plugins would be compatible with both `rubocop` and `standardrb`.
+Additionally, there's nothing that would prevent other tools like
+[rufo](https://github.com/ruby-formatter/rufo) from adopting it.)
+
+## How to make a plugin
+
+If you want to make a plugin, the first thing you should do is extend
+[LintRoller::Plugin](/lib/lint_roller/plugin.rb) with a custom class. Let's take
+this example plugin for banana-related static analysis:
+
+```ruby
+module BananaRoller
+  class Plugin < LintRoller::Plugin
+    # `config' is a Hash of options passed to the plugin by the user
+    def initialize(config = {})
+      @alternative = config["alternative"] ||= "chocolate"
+    end
+
+    def about
+      LintRoller::About.new(
+        name: "banana_roller",
+        version: "1.0", # or, in a gem, probably BananaRoller::VERSION
+        homepage: "https://github.com/example/banana_roller",
+        description: "Configuration of banana-related code"
+      )
+    end
+
+    # `context' is an instance of LintRoller::Context provided by the runner
+    def supported?(context)
+      context.engine == :rubocop
+    end
+
+    # `context' is an instance of LintRoller::Context provided by the runner
+    def rules(context)
+      LintRoller::Rules.new(
+        type: :path,
+        config_format: :rubocop,
+        value: Pathname.new(__dir__).join("../../config/default.yml")
+      )
+    end
+  end
+end
+```
+
+And that's pretty much it. Just a declarative way to identify your plugin,
+detect whether it supports the given
+[LintRoller::Context](/lib/lint_roller_context.rb) (e.g. the current `runner`
+and `engine` and their respective `_version`s), for which the plugin will
+ultimately its configuration as a [LintRoller::Rules](/lib/lint_roller/rules.rb)
+object.
+
+## Packaging a plugin in a gem
+
+In order for a formatter to use your plugin, it needs to know what path to
+require as well as the name of the plugin class to instantiate and invoke.
+
+To make this work seamlessly for your users without additional configuration of
+their own, all you need to do is specify a metadata attribute called
+`default_lint_roller_plugin` in your gemspec.
+
+Taking [standard-custom](https://github.com/standardrb/standard-custom) as an
+example, its gemspec contains:
+
+```ruby
+Gem::Specification.new do |spec|
+  # …
+  spec.metadata["default_lint_roller_plugin"] = "Standard::Custom::Plugin"
+  # …
+end
+```
+
+Because gem specs are loaded by RubyGems and Bundler very early, remember to
+specify the plugin as a string representation of the constant, as load order
+usually matters, and most tools will need to be loaded before any custom
+extensions. Hence, `"Standard::Custom::Plugin"` instead of
+`Standard::Custom::Plugin`.
+
+## Using your plugin
+
+Once you've made your plugin, here's how it's configured from a Standard Ruby
+`.standard.yml` file.
+
+### If your plugin is packaged as a gem
+
+Packaging your plugin in a gem is the golden path, both because distributing
+code via [RubyGems.org](https://rubygems.org) is very neat, but also because it
+makes the least work for your users.
+
+If your gem name is `banana_roller` and you've set
+`spec.metadata["default_lint_roller_plugin"]` to `"BananaRoller::Plugin"`, then
+your users could just add this to their `.standard.yml` file:
+
+```yaml
+plugins:
+  - banana_roller
+```
+
+And that's it! During initialization, `standardrb` will `require
+"banana_roller"` and know to call `BananaRoller::Plugin.new(config)` to
+instantiate it.
+
+### If your plugin ISN'T in a gem
+
+If you're developing a plugin for internal use or in conjunction with a single
+project, you may want it to live in the same repo as opposed to packaging it in
+a gem.
+
+To do this, then—in lieu of a gem name—provide the path you want to be required
+as its name, and (since there is no `spec.metadata` to learn of your plugin's
+class name), specify it as an option on the plugin:
+
+```yaml
+plugins:
+  - lib/banana_roller/plugin:
+      plugin_class_name: BananaRoller::Plugin
+```
+
+(Be careful with the indentation here! Any configuration under a plugin must be
+indented in order for it to be parsed as a hash under the
+`"lib/banana_roller/plugin"` key.)
+
+Additionally, if you want the plugin's name to make more sense, you can give
+it whatever name you like in the configuration and specify the `require_path`
+explicitly:
+
+```yaml
+plugins:
+  - banana_roller:
+      require_path: lib/banana_roller/plugin
+      plugin_class_name: BananaRoller::Plugin
+```
+
+### Passing user configuration to the plugin
+
+When a `LintRoller::Plugin` is instantiated, users can pass a configuration hash
+that tells your plugin how to behave.
+
+To illustrate how this works in Standard Ruby, anything passed as a hash beneath
+a plugin will be passed to the class's `initialize` method:
+
+```yaml
+plugins:
+  - apple_roller
+  - banana_roller:
+      require_path: lib/banana_roller/plugin
+      plugin_class_name: BananaRoller::Plugin
+      alternative: "apples"
+  - orange_roller:
+      rind: false
+```
+
+In the above case, `apple_roller`'s plugin class will be instantiated with
+`new({})`, `banana_roller` will get all 3 of those parameters passed
+`BananaRoller::Plugin.new({require_path…})`, and `orange_roller`'s class will be
+called with `new({rind: false})`.
+
+## Code of Conduct
+
+This project follows Test Double's [code of
+conduct](https://testdouble.com/code-of-conduct) for all community interactions,
+including (but not limited to) one-on-one communications, public posts/comments,
+code reviews, pull requests, and GitHub issues. If violations occur, Test Double
+will take any action they deem appropriate for the infraction, up to and
+including blocking a user from the organization's repositories.

data/vendor/bundle/ruby/{3.4.0/gems/loofah-2.24.0 → 4.0.0/gems/loofah-2.25.1}/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 2.25.1 / 2026-03-17
+
+* Ensure `Loofah::HTML5::Scrub.allowed_uri?` recognizes unescaped whitespace entities and rejects schemas containing them. See [GHSA-46fp-8f5p-pf2m](https://github.com/flavorjones/loofah/security/advisories/GHSA-46fp-8f5p-pf2m). #302 @flavorjones
+
+## 2.25.0 / 2025-12-15
+
+* Extract `Loofah::HTML5::Scrub.allowed_uri?` which operates on a string. Previously this logic was coupled to the parsed tree in `.scrub_uri_attribute`. #300 @flavorjones
+* Tightened up how entities and control characters are handled when detecting allowed URIs. #301 @flavorjones
+
+
+## 2.24.1 / 2025-05-12
+
+### Ruby support
+
+* Import only what's needed from `cgi` for support for Ruby 3.5 #296 @Earlopain
+
+
 ## 2.24.0 / 2024-12-24
 
 ### Added