Bump appsignal from 3.7.5 to 3.12.4

[dependabot]

Bumps appsignal from 3.7.5 to 3.12.4.

Changelog

Sourced from appsignal's changelog.

AppSignal for Ruby gem Changelog

3.12.3

Published on 2024-07-30.

Fixed

• Fix the application environment being reported as "[]" when no valid environment could be found. (patch cf081253)
• Fix Appsignal.configure call without env argument not reusing the previously configured configuration. (patch 65d5428c)

3.12.2

Published on 2024-07-25.

Fixed

• Fix the default env and root path for the integrations using loader mechanism. If APPSIGNAL_APP_ENV is set when using Appsignal.load(...), the AppSignal env set in APPSIGNAL_APP_ENV is now leading again. (patch b2d1c7ee)

3.12.1

Published on 2024-07-25.

Fixed

• Fix Appsignal.monitor_and_stop block passing. It would error with a LocalJumpError. Thanks to @​cwaider. (patch 150569ff)

3.12.0

Published on 2024-07-22.

Added

• Add a Rails configuration option to start AppSignal after Rails is initialized. By default, AppSignal will start before the Rails initializers are run. This way it is not possible to configure AppSignal in a Rails initializer using Ruby. To configure AppSignal in a Rails initializer, configure Rails to start AppSignal after it is initialized.

  # config/application.rb
  ...
  module MyApp
  class Application < Rails::Application
  # Add this line
  config.appsignal.start_at = :after_initialize
  # Other config
  
  end
  end

... (truncated)

Commits

• 64b06b1 Publish package v3.12.4
• 03d8dc9 Merge pull request #1226 from appsignal/fix-viewcomponent-event-formatter
• 0f37fa3 Always register ViewComponent event formatter
• 98fae7e Publish package v3.12.3
• 65d5428 Fix configure call without env when it has config (#1220)
• cf08125 Fix app env being reported as empty brackets (#1219)
• 53aa75d Publish package v3.12.2
• b2d1c7e Fix loader defaults from overriding other sources (#1214)
• e415fce Publish package v3.12.1
• 150569f Fix .monitor_and_stop block passing (#1211)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #176.