build(deps): bump github.com/newrelic/go-agent/v3 from 3.33.1 to 3.37.0 in /fibernewrelic

[dependabot]

Bumps github.com/newrelic/go-agent/v3 from 3.33.1 to 3.37.0.

Release notes

Sourced from github.com/newrelic/go-agent/v3's releases.

Release 3.37.0

3.37.0

Enhanced

• Implemented a new approach to integrating New Relic with SLOG that is more lightweight, out of the way, and collects richer data. These changes have been constructed to be completely backwards-compatible with v1 of nrslog. Changes include:
  • Wrapping slog.Handler objects with errors to allow users to handle invalid use cases
  • A complete rework of log enrichment so that New Relic linking metadata does not invalidate JSON, BSON, or YAML scanners. This new approach will instead inject the linking metadata as a key-value pair.
  • Complete support for With(), WithGroup(), and attributes for automatic instrumentation.
  • Performance operations.
  • Robust testing (close to 90% coverage).
  • This updates logcontext-v2/nrslog to v1.4.0.
• Now custom application tags (labels) may be added to all forwarded log events.
  • Enabled if ConfigAppLogForwardingLabelsEnabled(true) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED=TRUE
  • May exclude labels named in ConfigAppLogForwardingLabelsExclude("label1","label2",...) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE="label1,label2,..."
  • Labels are defined via ConfigLabels(...) or NEW_RELIC_LABELS
• Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality, report custom metrics or events, or take other appropriate actions, in response to rising heap memory size.

Fixed

• Added protection around transaction methods to gracefully return when the transaction object is nil.

Support statement

We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy for details about supported versions of the Go agent and third-party components.

Release 3.36.0

3.36.0

Enhanced

• Internal improvements to securityagent integration to better support trace handling and other support for security analysis of applications under test, now v1.3.4; affects the following other integrations:
  • nrecho, now v1.1.4
  • nrecho-v4, now v1.1.3
  • nrgin, now v1.3.3
  • nrgorilla, now v1.2.3
  • nrgraphqlgo, now v1.0.2
  • nrhttprouter, now v1.1.3

Fixed

• Added missing license files.
• Fixed module dependencies in nrgrpc integration, now v1.4.5
• Corrects handling of panic(nil) to no longer try to keep pre-Go-1.21 behavior but to allow newer language semantics for that condition. Fixes issue 975.

Support statement

We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy for details about supported versions of the Go agent and third-party components.

Release 3.35.1

Hotfix Release

This release was developed to quickly patch an issue with the registration of the New Relic Security Agent.

Fixed

... (truncated)

Changelog

Sourced from github.com/newrelic/go-agent/v3's changelog.

3.37.0

Enhanced

• Implemented a new approach to integrating New Relic with SLOG that is more lightweight, out of the way, and collects richer data. These changes have been constructed to be completely backwards-compatible with v1 of nrslog. Changes include:
  • Wrapping slog.Handler objects with errors to allow users to handle invalid use cases
  • A complete rework of log enrichment so that New Relic linking metadata does not invalidate JSON, BSON, or YAML scanners. This new approach will instead inject the linking metadata as a key-value pair.
  • Complete support for With(), WithGroup(), and attributes for automatic instrumentation.
  • Performance operations.
  • Robust testing (close to 90% coverage).
  • This updates logcontext-v2/nrslog to v1.4.0.
• Now custom application tags (labels) may be added to all forwarded log events.
  • Enabled if ConfigAppLogForwardingLabelsEnabled(true) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED=TRUE
  • May exclude labels named in ConfigAppLogForwardingLabelsExclude("label1","label2",...) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE="label1,label2,..."
  • Labels are defined via ConfigLabels(...) or NEW_RELIC_LABELS
• Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality, report custom metrics or events, or take other appropriate actions, in response to rising heap memory size.

Fixed

• Added protection around transaction methods to gracefully return when the transaction object is nil.

Support statement

We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy for details about supported versions of the Go agent and third-party components.

3.36.0

Enhanced

• Internal improvements to securityagent integration to better support trace handling and other support for security analysis of applications under test, now v1.3.4; affects the following other integrations:
  • nrecho, now v1.1.4
  • nrecho-v4, now v1.1.3
  • nrgin, now v1.3.3
  • nrgorilla, now v1.2.3
  • nrgraphqlgo, now v1.0.2
  • nrhttprouter, now v1.1.3

Fixed

• Added missing license files.
• Fixed module dependencies in nrgrpc integration, now v1.4.5
• Corrects handling of panic(nil) to no longer try to keep pre-Go-1.21 behavior but to allow newer language semantics for that condition. Fixes issue 975.

Support statement

We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy for details about supported versions of the Go agent and third-party components.

3.35.1

Fixed

• Security Agent Bug Hotfix: Do not update the security agent unti the go agent has completed its connect process PR
• Faster Trace ID generation
  • Community Member @​ankon contributed this change

Support statement

... (truncated)

Commits

• c081f78 Merge pull request #1004 from newrelic/develop
• 7043c7a Merge pull request #1003 from nr-swilloughby/release_3_37_0
• 2f2a7fe typo in changelog
• f6ca661 fixed nil transaction handling in StartSegment transaction method, preparatio...
• 9e8e9fb Merge pull request #996 from nr-swilloughby/oom_heap_callback
• f7b3d99 Merge branch 'develop' into oom_heap_callback
• a5ec16d Custom log tagging (labels) on forwarded application log events (#1002)
• d55d218 prevent all transaction methods from nil transaction errors (#1001)
• 18613dc Merge pull request #997 from iamemilio/slog-2.0
• e9de240 improved storage and caching of pre-compiled attributes and groups
• 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)

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (4)

• (deps)
• build(deps)
• bumb
• fix(deps)

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.