Update appsignal requirement from ~> 2 to ~> 3

[dependabot[bot]]

Updates the requirements on appsignal to permit the latest version.

Changelog

Sourced from appsignal's changelog.

3.5.5

Published on 2024-02-01.

Added

• d44f7092 patch - Add support for the redis-client gem, which is used by the redis gem since version 5.

Changed

• 6b9b814d patch - Make the debug log message for OpenTelemetry spans from libraries we don't automatically recognize more clear. Mention the span id and the instrumentation library.
• 6b9b814d patch - Fix an issue where queries containing a MySQL leading type indicator would only be partially sanitised.

Fixed

• e0f7b0e5 patch - Add more testing to JRuby extension installation to better report the installation result and any possible failures.

3.5.4

Changed

• 1a863490 patch - Fix disk usage returning a Vec with no entries on Alpine Linux when the df --local command fails.

Deprecated

• bb98744b patch - Deprecate the Appsignal.set_host_guage and Appsignal.set_process_gauge helper methods in the Ruby gem. These methods would already log deprecation warnings in the appsignal.log file, but now also as a Ruby warning. These methods will be removed in the next major version. These methods already did not report any metrics, and still do not.

Removed

• 1a863490 patch - Remove the appsignal_set_host_guage and appsignal_set_process_gauge extension functions. These functions were already deprecated and did not report any metrics.

Fixed

• 0637b71d patch - Fix the Makefile log path inclusion in the diagnose report. The diagnose tool didn't look in the correct gem extension directory for this log file.
• fe71d78b patch - Fix reporting of the Ruby syntax version and JRuby version in install report better.

3.5.3

Changed

• 50708677 patch - Log a warning when no mountpoints are found to report the disk usage metrics. This scenario shouldn't happen (it should log an error, message about skipping a mountpoint or log the disk usage). Log a warning to detect if this issue really occurs.

3.5.2

Fixed

• a5963f65 patch - Fix Ruby Logger 1.6.0 compatibility

3.5.1

... (truncated)

Commits

• 4c2845c Publish package v3.5.5
• 56dc710 Update supported gems in environment metadata (#1036)
• b8d8f38 Rename the internal logger method (#1035)
• ed1a20f Merge pull request #1034 from appsignal/bump-agent-0.31.2
• 612b9fc Fix diagnose tests agent version matcher
• 66bdef2 Remove changesets present in previous release
• 6b9b814 Bump agent to version 0.31.2
• 0d59333 Merge pull request #1028 from jbockler/redis-client-support
• e0f7b0e Test extension during JRuby install (#1031)
• d44f709 Add redis-client support
• 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)