appsignal 4.2.0 → 4.5.17

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 83c3f6a3607f3e28d1b95b790b1eec081673e596db8ed02a868bc31eb54fe884
-  data.tar.gz: a2f57f3c3604fb05953949114cf2e3a315c0ab61af40c0d50ee59a2a0c23a87a
+  metadata.gz: 9b41543a5c8a4ab168f9e25cb08cb21cac1f2feab07e2ee94948cb3b5e4a93de
+  data.tar.gz: 27cd215ac772b9df1fd0851b0b7cbad6c201d273ddc9d416cf739b928c632c0a
 SHA512:
-  metadata.gz: 108fd4431a1fd08f619ff084b8304dddd25bfc1cadf218265bdc12f7dc3e7609a551daa2b6e1a9c433dcdca5a51bccf5c916be12700bdd880b03aca422d03ca0
-  data.tar.gz: 1243f5f9894c7c7750bbd991a4e9dc7b6b8c5d80f4fd68e77798cccb97b41dc7efd7039e4e3176178f9fda0804c67643f2770098d34ff8c4105f8005320a6799
+  metadata.gz: 972b6a1e047559e8b5821e6e3749e25b22226f1a3064afbbe1d75f72d5f91882bcb2eee7dab8f7098a58c4419e272e0cb91e8b5ce74f94468f7942b96400502d
+  data.tar.gz: 257ffe63d397bd648fefbf055fd5955851a6a95f605f810c5e2fc6cb0aef5bc5584b34487a4d0625dec08e73f1fd77ca15840a5d2fbd5d669f3c4c0f482817de

data/CHANGELOG.md

@@ -1,5 +1,448 @@
 # AppSignal for Ruby gem Changelog
 
+## 4.5.17
+
+_Published on 2025-07-01._
+
+### Fixed
+
+- When an `Appsignal::Logger` uses `.broadcast_to` to broadcast messages to other loggers, broadcast those messages even if the log level of those messages is lower than the logger's threshold. This allows other loggers to set their own logging thresholds.
+
+  When the logger is silenced, messages below the silencing threshold are *not* broadcasted to other loggers.
+
+  (patch [bd3f2147](https://github.com/appsignal/appsignal-ruby/commit/bd3f2147ec58f5ed8c6db49328429e30e1826800))
+- When an `Appsignal::Logger` uses `.broadcast_to` to broadcast messages to other loggers, broadcast the original message received by the logger, without formatting it or converting it to a string. (patch [bd3f2147](https://github.com/appsignal/appsignal-ruby/commit/bd3f2147ec58f5ed8c6db49328429e30e1826800))
+- Call the `Appsignal::Logger` formatter with the original message object given, rather than converting it to a string before calling the formatter. (patch [bd3f2147](https://github.com/appsignal/appsignal-ruby/commit/bd3f2147ec58f5ed8c6db49328429e30e1826800))
+- When an error is passed to an `Appsignal::Logger` as the message, format it regardless of the logging level. Previously it would only be formatted when passed to `#error`. (patch [bd3f2147](https://github.com/appsignal/appsignal-ruby/commit/bd3f2147ec58f5ed8c6db49328429e30e1826800))
+- Ignore `Errno::ECONNRESET` errors in the Rack wrapper. (patch [90b0b7a3](https://github.com/appsignal/appsignal-ruby/commit/90b0b7a3e14832cb3626adf4b339bee56ba9745e))
+
+## 4.5.16
+
+_Published on 2025-06-27._
+
+### Changed
+
+- Log the error's backtrace on extension download failure. This will help us debug issues related to downloading the extension. (patch [71b7b9fe](https://github.com/appsignal/appsignal-ruby/commit/71b7b9fe7e929857968b69afcaa957be2ac2150a))
+
+### Fixed
+
+- Fix non-canonical rendering event paths for Capistrano deployments (patch [84e3c5c5](https://github.com/appsignal/appsignal-ruby/commit/84e3c5c597589e9e4cd34f9dbf1062c337570275))
+
+## 4.5.15
+
+_Published on 2025-06-06._
+
+### Added
+
+- Add `nginx_port` configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes [the NGINX metrics server](https://docs.appsignal.com/metrics/nginx.html). (patch [16976de8](https://github.com/appsignal/appsignal-ruby/commit/16976de8ad3cedda2b6ba3986c325728f5629f50))
+
+## 4.5.14
+
+_Published on 2025-05-27._
+
+### Fixed
+
+- Resolve problems with transactions not being properly closed when using libraries that change Fibers during the transactions. Previously, completed transactions would be attempted to be reused when creating a transaction, when the Fiber would be switched during a transaction. (patch [32733b25](https://github.com/appsignal/appsignal-ruby/commit/32733b25ced393cc7ed4bd6f15f3b6b293b133c5))
+- Fix a config error log message when the config is not active and should not validate the config. (patch [0d114b43](https://github.com/appsignal/appsignal-ruby/commit/0d114b435f63fe11bebce26efe282f90e2eb57aa))
+
+## 4.5.13
+
+_Published on 2025-05-12._
+
+### Fixed
+
+- Fix the C extension function definitions. On install, the Ruby gem extension would print warnings or fail to compile. (patch [c93f8e20](https://github.com/appsignal/appsignal-ruby/commit/c93f8e20860168929721f0c2b3e642a02dbde936))
+
+## 4.5.12
+
+_Published on 2025-05-12._
+
+### Added
+
+- Report the Active Job queue time as the `active_job_queue_time` metric. This metric can be used to track the queue time per Active Job queue. (patch [906f4458](https://github.com/appsignal/appsignal-ruby/commit/906f4458ceab3a922ffb1437e5bc85416589b809))
+
+## 4.5.11
+
+_Published on 2025-05-08._
+
+### Changed
+
+- Log a debug message when the reported error is ignored by the `ignore_errors` config option. (patch [0cda9da0](https://github.com/appsignal/appsignal-ruby/commit/0cda9da0c47c56bee39b6e045be36655dd13ee54))
+
+## 4.5.10
+
+_Published on 2025-05-05._
+
+### Changed
+
+- Remove redundant cron check-in pairs. When more than one pair of start and finish cron check-in events is reported for the same identifier in the same period, only one of them will be reported to AppSignal. (patch [803a0389](https://github.com/appsignal/appsignal-ruby/commit/803a03893aaf83391129b0b30cda169c8922a870))
+
+## 4.5.9
+
+_Published on 2025-04-09._
+
+### Fixed
+
+- Ensure request transactions are always closed in the `Rack::EventHandler`. A problem with Fibers changing during a request would cause transactions transactions to be left open and the data from requests to not be sent to our servers. (patch [52a72395](https://github.com/appsignal/appsignal-ruby/commit/52a72395b99a44d451fdc4026acfeb0cc2a5c23b))
+
+## 4.5.8
+
+_Published on 2025-04-04._
+
+### Added
+
+- Add the `enable_at_exit_hook` option to configure if `Appsignal.stop` is called when the Ruby application exits. Calling `Appsignal.stop` will stop the application for a moment to flush all the data to our agent before shutting down.
+
+  This option has three possible values:
+
+  - `always`: Always call `Appsignal.stop` when the program exits. On (Docker) containers it's automatically set to this value.
+  - `never`: Never call `Appsignal.stop` when the program exits. The default value when the program doesn't run on a (Docker) container.
+  - `on_error`: Call `Appsignal.stop` when the program exits with an error.
+
+  (patch [d0a5875c](https://github.com/appsignal/appsignal-ruby/commit/d0a5875cef5101680f1cab4649d71440212f9ea8), [043a6c74](https://github.com/appsignal/appsignal-ruby/commit/043a6c740b708e1182ed7161e3c9ad38bd3314de), [b680fe6f](https://github.com/appsignal/appsignal-ruby/commit/b680fe6f6b283205a13ca61bd4a26167f541dbca))
+
+### Deprecated
+
+- Deprecate the `Appsignal.monitor_and_stop` helper.
+
+  We instead recommend using the `Appsignal.monitor` helper and configuring the `enable_at_exit_hook` config option to `always`.
+
+  (patch [84969aea](https://github.com/appsignal/appsignal-ruby/commit/84969aeaca8f3737921e9adf1efdad55b52e1206))
+
+## 4.5.7
+
+_Published on 2025-03-20._
+
+### Added
+
+- Add the `Appsignal.config_error` and `Appsignal.config_error?` methods. This method contains any error that may have occurred while loading the `config/appsignal.rb` file. If it is `nil` no error occurred or `Appsignal.start` hasn't been called yet. The `Appsignal.config_error?` method is an alias for syntax sugar. (patch [0f3a7372](https://github.com/appsignal/appsignal-ruby/commit/0f3a73729306d96b630339ccf6e218318d1e2870))
+- Add the `check_if_started!` method. This method will raise an error if the AppSignal Ruby gem failed to start.
+
+  Call this method in your CI or on app boot if you wish to verify that AppSignal has started when your application does, and want the application to fail to start if AppSignal hasn't started.
+
+  For example, in this Rails initializer:
+
+  ```
+  # config/initializers/appsignal.rb
+
+  Appsignal.check_if_started!
+  ```
+
+  (patch [b41c9c99](https://github.com/appsignal/appsignal-ruby/commit/b41c9c991bdbcd64b7a04e9832b15ddacda7ae20))
+
+## 4.5.6
+
+_Published on 2025-03-20._
+
+### Added
+
+- Add the Logger `<<` method. This improves our compatibility with Ruby's Logger class implementation, making it usable in more scenarios. (patch [e09a78a4](https://github.com/appsignal/appsignal-ruby/commit/e09a78a425607852b5e12adf5c9ddb718811b09f))
+
+### Changed
+
+- Explicitly return `nil` from public methods with no usable return value. We want to avoid the situation where `Appsignal.start` happens to return `true` and it is thought to mean that the gem started successfully.
+
+  Methods updated:
+
+  - `Appsignal.start`
+  - `Appsignal.stop`
+  - `Appsignal.configure`
+  - `Appsignal.forked`
+  - `Appsignal.load`
+
+  (patch [93c304ee](https://github.com/appsignal/appsignal-ruby/commit/93c304eecd80992648d9e836a52e28c4e78958ee))
+- Differentiate between `process_request.rack` events. Add the callback that triggered the event in the event title for debugging purposes. (patch [4393b2fa](https://github.com/appsignal/appsignal-ruby/commit/4393b2faeac6d8be6390eef158b3cda133b99915))
+- Improve the log message for the uneven timestack error. This will help the AppSignal team debug issues where events get closed when all events are already closed. (patch [d2d4863f](https://github.com/appsignal/appsignal-ruby/commit/d2d4863fc8421eabb4c88e945bb24243a56535d3))
+
+## 4.5.5
+
+_Published on 2025-03-14._
+
+### Changed
+
+- Improve SQL sanitisation for functions and numbered placeholders. (patch [316f1205](https://github.com/appsignal/appsignal-ruby/commit/316f12050bd4e1391a50ff72989aabbdb7a09760))
+
+## 4.5.4
+
+_Published on 2025-03-11._
+
+### Changed
+
+- Delay and eventually halt agent reboots by the extension.
+
+  The AppSignal extension is responsible for booting the AppSignal agent. If communication with the agent is lost, the extension is responsible for rebooting it.
+
+  In certain scenarios, such as when several processes with different AppSignal configurations are misconfigured to share the same working directory, the processes' extensions can enter a loop of rebooting and killing each others' agents. These short-lived agents may then attempt to repeatedly send pending payloads to AppSignal in quick succession.
+
+  This change causes the extension to delay each reboot of its agent by one additional second, and to no longer attempt to reboot the agent after the tenth reboot, slowing down and eventually breaking this loop.
+
+  (patch [8c66c704](https://github.com/appsignal/appsignal-ruby/commit/8c66c7049b038bae8c52a833b39993f9160c2ae8))
+
+## 4.5.3
+
+_Published on 2025-03-06._
+
+### Changed
+
+- Specify stricter Rack version requirement. The Ruby gem relies on the `Rack::Events` constant which was introduced in Rack 2. Update our version requirement to require Rack 2 or newer. (patch [19bdb0b3](https://github.com/appsignal/appsignal-ruby/commit/19bdb0b3914e93e9f7c7ffa3a1bad80d9f3d1520))
+
+### Fixed
+
+- Fix the queue time reporting for Sidekiq 8 jobs. It would report high negative values for the queue time with Sidekiq 8. (patch [6fcc40e3](https://github.com/appsignal/appsignal-ruby/commit/6fcc40e31e8656cb84daa8bb5a0bea7a137ab089))
+
+## 4.5.2
+
+_Published on 2025-02-24._
+
+### Fixed
+
+- Validate application environment sources so nil values and empty strings are not valid app environments.
+  Symbols are now always cast to a String before set as the application environment.
+
+  ```ruby
+  # These will no longer be accepted as valid app environments
+  Appsignal.configure("")
+  Appsignal.configure(" ")
+  ```
+
+  (patch [bfe37be9](https://github.com/appsignal/appsignal-ruby/commit/bfe37be9ca14248f5e5a030d0cab42998d371d36))
+- Fix Capistrano version 2 and 3 support when using an `appsignal.rb` config file. It will now pick up the config from `appsignal.rb` file. (patch [2a694196](https://github.com/appsignal/appsignal-ruby/commit/2a6941967435d6672c122e0aa07ec9c2de3e30bc))
+
+## 4.5.1
+
+_Published on 2025-02-24._
+
+### Changed
+
+- [b3748870](https://github.com/appsignal/appsignal-ruby/commit/b3748870b0de1973566761308c365ce5c5de7d00) patch - Update bundled trusted root certificates
+
+## 4.5.0
+
+_Published on 2025-02-21._
+
+### Added
+
+- Add a helper to create custom markers from the Ruby gem.
+
+  Create a custom marker (a little icon shown in the graph timeline on AppSignal.com) to mark events on the timeline.
+
+  Create a marker with all the available options:
+
+  ```ruby
+  Appsignal::CustomMarker.report(
+    # The icon shown on the timeline
+    :icon => "🎉",
+    # The message shown on hover
+    :message => "Migration completed",
+    # Any time object or a string with a ISO8601 valid time is accepted
+    :created_at => Time.now
+  )
+  ```
+
+  Create a marker with just a message:
+
+  ```ruby
+  Appsignal::CustomMarker.report(
+    :message => "Migration completed",
+  )
+  ```
+
+  _The default icon is the 🚀 icon. The default time is the time the request is received by our servers._
+
+  (minor [e92c8c9d](https://github.com/appsignal/appsignal-ruby/commit/e92c8c9da6e0a159a4405ff178b346040db53fa4))
+
+### Removed
+
+- Remove the OpenTelemetry beta feature in favor of the new [AppSignal collector](https://docs.appsignal.com/collector). If you are using the AppSignal agent to send OpenTelemetry data in our public beta through the `/enriched` endpoint on the agent's HTTP server, please migrate to the collector to continue using the beta. The collector has a much better implementation of this feature for the beta. (minor [f934d0d4](https://github.com/appsignal/appsignal-ruby/commit/f934d0d496a61779d17caf01b4dff1e2c9f5b92e))
+
+## 4.4.0
+
+_Published on 2025-02-06._
+
+### Changed
+
+- Do not report error causes if the wrapper error has already been reported. This deduplicates errors and prevents the error wrapper and error cause to be reported separately, as long as the error wrapper is reported first.
+
+  ```ruby
+  error_wrapper = nil
+  error_cause = nil
+  begin
+    begin
+      raise StandardError, "error cause"
+    rescue => e
+      error_cause = e
+      raise Exception, "error wrapper"
+    end
+  rescue Exception => e
+    error_wrapper = e
+  end
+
+  Appsignal.report_error(error_wrapper) # Reports error
+  Appsignal.report_error(error_cause) # Doesn't report error
+  ```
+
+  (minor [af02b8b3](https://github.com/appsignal/appsignal-ruby/commit/af02b8b356f03b23efe83511970de62281837054))
+
+### Fixed
+
+- Fix an issue where the HTTP.rb gem integration would raise an error when a string containing non-ASCII characters is passed to the gem as the URL. (patch [fce0acdf](https://github.com/appsignal/appsignal-ruby/commit/fce0acdfe0a7f807c846c3f90fd79f994c44db0b))
+
+## 4.3.3
+
+_Published on 2025-01-17._
+
+### Added
+
+- Add support for the [Ownership](https://github.com/ankane/ownership) gem, which is used to mark different segments of the application as owned by specific teams.
+
+  The AppSignal sample will be tagged with the given owner:
+
+  ```ruby
+  class OrdersController < ApplicationController
+    owner :logistics
+    # Transactions for requests handled by this controller will be tagged
+    # in AppSignal with the "owner" tag set to "logistics"
+  end
+  ```
+
+  If several owners are set within the same transaction, the last owner will take precedence. If an error is reported in the transaction, the owner tag will be set to the owner that was set when the error was raised.
+
+  Set the [`ownership_set_namespace` configuration option](https://docs.appsignal.com/ruby/configuration/options.html#option-ownership_set_namespace) to `true` to also set the AppSignal sample's namespace to the owner. Note that doing so will cause existing performance and error incidents to be re-created with the new namespace.
+
+  Set the [`instrument_ownership` configuration option](https://docs.appsignal.com/ruby/configuration/options.html#option-instrument_ownership) to `false` to disable the integration with the Ownership gem.
+
+  (patch [865b348e](https://github.com/appsignal/appsignal-ruby/commit/865b348e1cf37193e3c31176dad47cbbd5d810bb))
+
+### Changed
+
+- Do not report `SystemExit` errors from our Rake integration. (patch [ad4f1a25](https://github.com/appsignal/appsignal-ruby/commit/ad4f1a250f00f1d1997932a3f108b0cf6b99ea43))
+- Do not report `SignalException` errors from our Rake integration. (patch [7c07a596](https://github.com/appsignal/appsignal-ruby/commit/7c07a59622426ca565c538a0c239270ebbd54f4c))
+
+### Fixed
+
+- Fix deprecation warnings when building the AppSignal gem's native extension on Ruby 3.4, by porting the extension to use the TypedData API. (patch [e2d186c9](https://github.com/appsignal/appsignal-ruby/commit/e2d186c9e79a5d03d3692c6ed84ca085e1383031))
+
+## 4.3.2
+
+_Published on 2024-12-31._
+
+### Fixed
+
+- Fix an issue where loggers, when broadcasted to by `Appsignal::Logger#broadcast_to`, would format again messages that have already been formatted by the broadcaster, causing the resulting message emitted by the logger to contain double newlines. (patch [cd2f9fbf](https://github.com/appsignal/appsignal-ruby/commit/cd2f9fbfe31b39de90bc012ddacaaf9b28fef913))
+
+## 4.3.1
+
+_Published on 2024-12-20._
+
+### Fixed
+
+- Fix a performance issue when sanitising `INSERT INTO ... VALUES` queries. (patch [9791d9a1](https://github.com/appsignal/appsignal-ruby/commit/9791d9a1ef18bd18b96ad449cae90425a621bfb3))
+
+## 4.3.0
+
+_Published on 2024-12-20._
+
+### Added
+
+- Add logger broadcasting. This change implements an alternative within `Appsignal::Logger` to `ActiveSupport::BroadcastLogger`, following the same interface. This enables a proper workaround to the issues with `ActiveSupport::BroadcastLogger` (([#49745](https://github.com/rails/rails/issues/49745), [#51883](https://github.com/rails/rails/issues/51883))) when used alongside tagged logging.
+
+  For example, to use tagged logging both in logs emitted by the default `Rails.logger` and in logs sent to AppSignal, replace the `Rails.logger` with an AppSignal logger that broadcasts to the default `Rails.logger`:
+
+  ```ruby
+  appsignal_logger = Appsignal::Logger.new("app")
+  appsignal_logger.broadcast_to(Rails.logger)
+  Rails.logger = ActiveSupport::TaggedLogging.new(appsignal_logger)
+  ```
+
+  (minor [5cb1464b](https://github.com/appsignal/appsignal-ruby/commit/5cb1464bcf12f043774fb55850e6b82aeba9c1ca))
+
+### Removed
+
+- Remove tagged logging support from `Appsignal::Logger`.
+
+  Tagged logging is still supported by wrapping an instance of `Appsignal::Logger` with `ActiveSupport::TaggedLogging`:
+
+  ```ruby
+  appsignal_logger = Appsignal::Logger.new("rails")
+  tagged_logger = ActiveSupport::TaggedLogging.new(appsignal_logger)
+  Rails.logger = tagged_logger
+  ```
+
+  Removing this functionality allows for a workaround to issues within Rails ([#49745](https://github.com/rails/rails/issues/49745), [#51883](https://github.com/rails/rails/issues/51883)), where using the broadcast logger to log to more than one tagged logger results in incorrect behaviour of the tagged logging methods, resulting in breakage throughout Rails' internals:
+
+  ```ruby
+  # We use the built-in request ID middleware as an example that triggers
+  # the issue:
+  Rails.config.log_tags = [:request_id]
+
+  appsignal_logger = Appsignal::Logger.new("rails")
+  tagged_logger = ActiveSupport::TaggedLogging.new(appsignal_logger)
+
+  # This does not work correctly, because the default `Rails.logger` is a
+  # broadcast logger that is already broadcasting to a tagged logger.
+  # When asked to broadcast to a second tagged logger, the return value of
+  # `Rails.logger.tagged { ... }` will be incorrect, in turn causing the
+  # `RequestID` middleware, which uses it internally, to return broken
+  # Rack responses.
+  Rails.logger.broadcast_to(tagged_logger)
+  ```
+
+  By reverting the changes to our logger so that it is no longer a tagged logger, we enable a workaround to this issue:
+
+  ```ruby
+  Rails.config.log_tags = [:request_id]
+
+  appsignal_logger = Appsignal::Logger.new("rails")
+
+  # This works correctly, because `appsignal_logger` is not a tagged logger.
+  # Note that `appsignal_logger` will not have the `request_id` tags.
+  Rails.logger.broadcast_to(appsignal_logger)
+  ```
+
+  (patch [c061aa4e](https://github.com/appsignal/appsignal-ruby/commit/c061aa4e3f9485a1549ea90316534cddd36e238e))
+
+### Fixed
+
+- Fix `#silence` implementation for `Appsignal::Logger`. (patch [d08a1cec](https://github.com/appsignal/appsignal-ruby/commit/d08a1cec705db71999afa9c4af36e244a7b6483a))
+
+## 4.2.3
+
+_Published on 2024-12-17._
+
+### Fixed
+
+- Fix tagged logging ArgumentError error for Rails 8. (patch [8f373074](https://github.com/appsignal/appsignal-ruby/commit/8f373074531d8285b4718c16e125a62f42774d90))
+
+## 4.2.2
+
+_Published on 2024-12-16._
+
+### Added
+
+- Support Rails/ActiveSupport tagged logging. When tags are set in apps using `Rails.logger.tagged { ... }` or with the `Rails.application.config.log_tags = [...]` config option, these tags are now included in the collected log messages.
+
+  ```ruby
+  Rails.logger.tagged(["Tag 1", "Tag 2"]) { Rails.logger.info("My message") }
+  ```
+
+  Reports this log message:
+
+  > [Tag 1] [Tag 2] My message
+
+  (patch [41e1e8f0](https://github.com/appsignal/appsignal-ruby/commit/41e1e8f076025da2420cb43c53b5f7211ae45de8))
+
+### Fixed
+
+- Fix a thread safety issue where sending check-in events simultaneously from different threads would cause several check-in schedulers to be initialised internally. This could cause some of the scheduled check-in events to never be sent to AppSignal when `Appsignal.stop` is called. (patch [c372a3f9](https://github.com/appsignal/appsignal-ruby/commit/c372a3f998b78ef5ef259be39fe198433d6ca95e))
+
+## 4.2.1
+
+_Published on 2024-12-04._
+
+### Changed
+
+- Minimize difference between Rack transaction duration and total child event durations. (patch [95c37802](https://github.com/appsignal/appsignal-ruby/commit/95c3780291241fa6de8d2c0ae9bb09d3ce42d18d))
+
 ## 4.2.0
 
 _Published on 2024-11-13._

data/README.md

@@ -9,9 +9,6 @@ issues.
 - [Ruby code documentation][ruby-doc]
 - [Support][contact]
 
-[![Gem Version](https://badge.fury.io/rb/appsignal.svg)](http://badge.fury.io/rb/appsignal)
-[![Code Climate](https://codeclimate.com/github/appsignal/appsignal.png)](https://codeclimate.com/github/appsignal/appsignal)
-
 ## Description
 
 The AppSignal gem collects exceptions and performance data from your Ruby

data/Rakefile

@@ -357,7 +357,7 @@ end
 begin
   require "rspec/core/rake_task"
   is_jruby = defined?(RUBY_ENGINE) && RUBY_ENGINE == "jruby"
-  excludes = []
+  excludes = ["spec/integration/diagnose/**/*_spec.rb"]
   excludes << "spec/lib/appsignal/extension/jruby_spec.rb" unless is_jruby
   exclude_pattern = "--exclude-pattern=#{excludes.join(",")}" if excludes.any?
 

data/appsignal.gemspec

@@ -57,7 +57,8 @@ Gem::Specification.new do |gem| # rubocop:disable Metrics/BlockLength
   }
 
   gem.add_dependency "logger"
-  gem.add_dependency "rack"
+  # Needs 2.0+ because we rely on Rack::Events
+  gem.add_dependency "rack", ">= 2.0.0"
 
   gem.add_development_dependency "pry"
   gem.add_development_dependency "rake", ">= 12"

data/build_matrix.yml

@@ -88,6 +88,8 @@ matrix:
       - "rails-8.0"
 
   ruby:
+    - ruby: "3.5.0-preview1"
+    - ruby: "3.4.1"
     - ruby: "3.3.4"
     - ruby: "3.2.5"
     - ruby: "3.1.6"
@@ -102,6 +104,8 @@ matrix:
     - gem: "dry-monitor"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -110,6 +114,8 @@ matrix:
     - gem: "hanami-2.0"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -117,6 +123,8 @@ matrix:
     - gem: "hanami-2.1"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -124,14 +132,19 @@ matrix:
     - gem: "hanami-2.2"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
     - gem: "http5"
+    - gem: "ownership"
     - gem: "padrino"
     - gem: "psych-3"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -140,6 +153,8 @@ matrix:
     - gem: "psych-4"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -165,6 +180,8 @@ matrix:
     - gem: "rails-7.0"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -174,6 +191,8 @@ matrix:
     - gem: "rails-7.1"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -182,6 +201,8 @@ matrix:
     - gem: "rails-7.2"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
           - "3.1.6"
@@ -189,6 +210,8 @@ matrix:
     - gem: "rails-8.0"
       only:
         ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
           - "3.3.4"
           - "3.2.5"
     - gem: "sequel"
@@ -196,3 +219,13 @@ matrix:
     - gem: "webmachine2"
     - gem: "redis-4"
     - gem: "redis-5"
+    - gem: "sidekiq-7"
+      only:
+        ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"
+    - gem: "sidekiq-8"
+      only:
+        ruby:
+          - "3.5.0-preview1"
+          - "3.4.1"