appsignal 4.10.3 → 4.10.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 412195cf8689cd4b5cf1354066084836998496671da0e214f7d27d96f7afa8d2
-  data.tar.gz: bf8d8ac65009cf0d1d4d72f5e6543028e1251816522d7a5fdd3d9638a717ce1a
+  metadata.gz: 62a84990c82bdbb5c3e59a42ab7d960d072b6a7ec5f44c5de53ac53e3863616d
+  data.tar.gz: f7b4bf9aac46c183ce5ff78387e7a4ab56f85f203efcf2f995701d5424517c7c
 SHA512:
-  metadata.gz: 45c4279e9634212527eda07c2343465e0c83bfc2dfe1539c32004a3495509909b6ed9435c01243b6b949254fa3904765989542ddb429df67ecfade9ef0341119
-  data.tar.gz: dbcb1e1affec1bd33584528e00b779e21c4c77e91c48c354477167bf45b76e38c61c32f04a8f1bea58e62e85c992030cde8414f3234e6a28192b3460baa4b050
+  metadata.gz: cd585c612e66a3b88e86d93a05d260affbb35d8c2d1ff921a52f6ae00b4e89ff3f5e4b6ba4edff657b771d5756a5c41f4b3081eafecd778548f11ef08b54f656
+  data.tar.gz: e3040b1ad97a20dbfe94fe80345489a22d8de81c907df61180d5e247553122c92dcd146be3b7b37cb665b6db28d454bf580e1e05345e52a61270da31d6774360

data/CHANGELOG.md

@@ -1,5 +1,20 @@
 # AppSignal for Ruby gem Changelog
 
+## 4.10.4
+
+_Published on 2026-09-22._
+
+### Fixed
+
+- Start AppSignal before the Rails application's initializers run. Depending on
+  the order in which gems were loaded, AppSignal could start after
+  `config/initializers`. In those applications `Appsignal.active?` returned
+  `false` inside an initializer, errors raised by initializers were not reported,
+  and with `config.appsignal.start_at = :after_initialize` the Rails defaults for
+  `log_path` and `ignore_actions` were not applied.
+
+  (patch [523d8458](https://github.com/appsignal/appsignal-ruby/commit/523d845879cfe8cc6306bdc24d51f88ad979f714))
+
 ## 4.10.3
 
 _Published on 2026-09-10._

data/lib/appsignal/integrations/railtie.rb

@@ -13,8 +13,10 @@ module Appsignal
       config.appsignal = ActiveSupport::OrderedOptions.new
       config.appsignal.start_at = :on_load
 
-      # Run after the Rails framework is loaded
-      initializer "appsignal.configure_rails_initialization" do |app|
+      # Runs before `load_config_initializers` so that AppSignal has started
+      # when the app's initializers run, and errors they raise are reported.
+      initializer "appsignal.configure_rails_initialization",
+        :before => :load_config_initializers do |app|
         Appsignal::Integrations::Railtie.on_load(app)
       end
 

data/lib/appsignal/version.rb

@@ -2,5 +2,5 @@
 
 module Appsignal
   # @return [String]
-  VERSION = "4.10.3"
+  VERSION = "4.10.4"
 end

data/sig/appsignal.rbi

@@ -8,7 +8,7 @@
 module Appsignal
   extend Appsignal::Helpers::Metrics
   extend Appsignal::Helpers::Instrumentation
-  VERSION = T.let("4.10.3", T.untyped)
+  VERSION = T.let("4.10.4", T.untyped)
 
   class << self
     # The loaded AppSignal configuration.

metadata

@@ -1,16 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: appsignal
 version: !ruby/object:Gem::Version
-  version: 4.10.3
+  version: 4.10.4
 platform: ruby
 authors:
 - Robert Beekman
 - Thijs Cadier
 - Tom de Bruijn
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-10 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logger
@@ -324,7 +323,6 @@ metadata:
   documentation_uri: https://docs.appsignal.com/ruby/
   homepage_uri: https://docs.appsignal.com/ruby/
   source_code_uri: https://github.com/appsignal/appsignal-ruby
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -340,8 +338,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.22
-signing_key:
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Logs performance and exception data from your app to appsignal.com
 test_files: []