Skip to content

Update dependency sentry/sentry-symfony to v5.15.0 - #2658

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/services/sentry-sentry-symfony-5.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/services/sentry-sentry-symfony-5.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
sentry/sentry-symfony (source) 5.12.0 → 5.15.0 age confidence

Release Notes

getsentry/sentry-symfony (sentry/sentry-symfony)

v5.15.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v5.15.0.

Features
  • Add the experimental register_monolog_handler option, which captures errors through the Monolog channels Symfony reports them to instead of the SDK's global error handlers. (#​1092)

    sentry:
        register_error_listener: false
        register_error_handler: false
        register_monolog_handler: true
  • Add the $includeChannel argument to the Monolog LogsHandler, which attaches the Monolog channel as a channel attribute to logs. (#​1091)

    services:
        Sentry\SentryBundle\Monolog\LogsHandler:
            arguments:
                $level: !php/const Monolog\Logger::WARNING
                $includeChannel: true
Bug fixes
  • Fix empty response bodies from the PSR-18 clients when HTTP client tracing is enabled on Symfony HttpClient 6.4.49, 7.4.22 and 8.1.10. (#​1099)

v5.14.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v5.14.0.

Features
  • Add the data_collection option to control which potentially sensitive data the SDK attaches to events and spans. (#​1087)

    sentry:
        options:
            data_collection:
                user_info: true
                http_headers:
                    mode: allowList
                    terms:
                        - x-request-id
                http_bodies: []
                database_query_data: false
Bug fixes
  • Set the user context before the router runs, so that events for unmatched routes include the client IP address. (#​1068)
Misc

v5.13.0

Compare Source

The Sentry SDK team is happy to announce the immediate availability of Sentry Symfony SDK v5.13.0.

Misc

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from ryanmab as a code owner October 21, 2026 19:23
@renovate renovate Bot added bump-patch Pull request which needs to bump a patch version in this repository. chore Pull requests that resolve chores (for releases) dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Oct 21, 2026
@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/orchestrator/infrastructure in the prod workspace
With var files: ./services/orchestrator/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.orchestrator.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-orchestrator-prod"
!~      last_modified                  = "2026-10-21T19:18:41.000+0000" -> (known after apply)
!~      source_code_hash               = "ZooNMsQekn7Hgv1eZZWAAuzc19xDsgpypilSaj8brnc=" -> "skNy09xaeBPOMfygEmqLiuOG1TGg3/Ku1ayS0zy4p5I="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Warning: Argument is deprecated

  with module.event_store.aws_dynamodb_table.event_table,
  on event_store/main.tf line 1, in resource "aws_dynamodb_table" "event_table":
   1: resource "aws_dynamodb_table" "event_table" {

range_key is deprecated. Use key_schema instead.

(and one more similar warning elsewhere)

📝 Plan generated in Orchestrator #2662

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/ingest/infrastructure in the prod workspace
With var files: ./services/ingest/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.ingest.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-ingest-prod"
!~      last_modified                  = "2026-10-21T19:19:12.000+0000" -> (known after apply)
!~      source_code_hash               = "YB5eU4Sk6TyoBJG3r+aYNaSY4FajZRLe0ybJ+y6Ffws=" -> "HLQzm8q4W4NjeQX4GfKfC4im0x6yF3J/3ZWgqLXh5Hg="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Ingest #3637

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/publish/infrastructure in the prod workspace
With var files: ./services/publish/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.publish.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-publish-prod"
!~      last_modified                  = "2026-10-21T19:19:01.000+0000" -> (known after apply)
!~      source_code_hash               = "ixRCUlILQ9xZ/BhGCm+pMoylYcKOpXOzJEWMwThOUq4=" -> "lRtQNBRNcIEyjREsgAxpIU6Y6I4gktbvlNWvecdxxmo="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Publish #2854

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/api/infrastructure in the prod workspace
With var files: ./services/api/infrastructure/prod.tfvars

Plan: 0 to add, 3 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.api.aws_lambda_function.api will be updated in-place
!~  resource "aws_lambda_function" "api" {
        id                             = "coverage-api-prod"
!~      last_modified                  = "2026-10-21T19:19:47.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "9oFq9D7lulxJhL2NJrRAntGONm3e76JmT1QoWQlROxc="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

  # module.event_listener.aws_lambda_function.events will be updated in-place
!~  resource "aws_lambda_function" "events" {
        id                             = "coverage-api-event-listener-prod"
!~      last_modified                  = "2026-10-21T19:19:30.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "9oFq9D7lulxJhL2NJrRAntGONm3e76JmT1QoWQlROxc="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

  # module.webhook_handler.aws_lambda_function.webhooks will be updated in-place
!~  resource "aws_lambda_function" "webhooks" {
        id                             = "coverage-api-webhook-handler-prod"
!~      last_modified                  = "2026-10-21T19:19:39.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "9oFq9D7lulxJhL2NJrRAntGONm3e76JmT1QoWQlROxc="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 3 to change, 0 to destroy.

📝 Plan generated in API #3661

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/analyse/infrastructure in the prod workspace
With var files: ./services/analyse/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.analyse.aws_lambda_function.analyse will be updated in-place
!~  resource "aws_lambda_function" "analyse" {
        id                             = "coverage-analyse-prod"
!~      last_modified                  = "2026-10-21T19:19:06.000+0000" -> (known after apply)
!~      source_code_hash               = "fhjUgdyYs4ibQ72cuaShYuL1BPAbhJ+SggiSBWCcfis=" -> "A+jPxVYLFEZjgESNGmYjdBUlu4GlC9VNYC/tax7BihQ="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Analyse #3956

@coverage-robot

coverage-robot Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Coverage Report

Merging #2658 will not change the total coverage (compared to bc7d564)

Total Coverage Diff Coverage
78.03% ø
Tags
Tag Lines Covered Partial Uncovered Coverage
analyse-service 2430 2124 0 306 87.41%
api-service 1420 1015 0 405 71.48%
clients-package
(Carried forward from dd22fbc)
95 88 0 7 92.63%
configuration-package
(Carried forward from dd22fbc)
665 513 0 152 77.14%
event-package
(Carried forward from dd22fbc)
166 107 0 59 64.46%
ingest-service 1040 852 0 188 81.92%
local-package
(Carried forward from dd22fbc)
250 169 0 81 67.6%
message-package
(Carried forward from dd22fbc)
92 56 0 36 60.87%
orchestrator-service 850 704 0 146 82.82%
publish-service 1113 718 0 395 64.51%
telemetry-package
(Carried forward from dd22fbc)
108 75 0 33 69.44%
Impacted Files

No impacted files in #2658

Last update to 5286c49 at 03:41am UTC

@renovate
renovate Bot force-pushed the renovate/services/sentry-sentry-symfony-5.x-lockfile branch from 0abf99a to 5286c49 Compare October 30, 2026 03:38
@renovate renovate Bot changed the title Update dependency sentry/sentry-symfony to v5.14.0 Update dependency sentry/sentry-symfony to v5.15.0 Oct 30, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump-patch Pull request which needs to bump a patch version in this repository. chore Pull requests that resolve chores (for releases) dependencies Pull requests that update a dependency file php Pull requests that update Php code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants