Bump appsignal from 4.3.2 to 4.3.3

[dependabot]

Bumps appsignal from 4.3.2 to 4.3.3.

Changelog

Sourced from appsignal's changelog.

4.3.3

Published on 2025-01-17.

Added

• Add support for the 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:

  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 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 to false to disable the integration with the Ownership gem.

  (patch 865b348e)

Changed

• Do not report SystemExit errors from our Rake integration. (patch ad4f1a25)
• Do not report SignalException errors from our Rake integration. (patch 7c07a596)

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)

Commits

• c181025 Publish package v4.3.3
• c307d46 Merge pull request #1364 from appsignal/ownership-integration
• 0f2a138 Merge pull request #1368 from appsignal/require-logger-rails-7-concurrent-ruby
• 3233bfb Require logger before all other gems
• 865b348 Instrument ownership gem
• 6a23a28 Add before_complete transaction hook
• a876b71 Add after_create transaction hook
• d217cea Add ownership_set_namespace config option
• ba55c63 Merge pull request #1365 from appsignal/ignore-rake-systemexit-error
• 7c07a59 Do not report SignalException from Rake tasks
• 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]

Looks like appsignal is up-to-date now, so this is no longer needed.