25494 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
dependabot[bot]	70e6cc01e5	Bump pyo3-log from 0.13.1 to 0.13.2 (#19156) ... Bumps [pyo3-log](https://github.com/vorner/pyo3-log) from 0.13.1 to 0.13.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vorner/pyo3-log/blob/main/CHANGELOG.md">pyo3-log's changelog</a>.</em></p> <blockquote> <h1>0.13.2</h1> <ul> <li>Support for pyo3 0.27 (<a href="https://redirect.github.com/vorner/pyo3-log/issues/72">#72</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="9674e2d39c"><code>9674e2d</code></a> Version 0.13.2</li> <li><a href="c51e45a9cd"><code>c51e45a</code></a> Bump <code>pyo3</code> to 0.27 (<a href="https://redirect.github.com/vorner/pyo3-log/issues/72">#72</a>)</li> <li>See full diff in <a href="https://github.com/vorner/pyo3-log/compare/v0.13.1...v0.13.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-10 23:36:08 +00:00
dependabot[bot]	91c2845180	Bump pydantic from 2.12.3 to 2.12.4 (#19158) ... Bumps [pydantic](https://github.com/pydantic/pydantic) from 2.12.3 to 2.12.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/releases">pydantic's releases</a>.</em></p> <blockquote> <h2>v2.12.4 2025-11-05</h2> <h2>v2.12.4 (2025-11-05)</h2> <p>This is the fourth 2.12 patch release, fixing more regressions, and reverting a change in the <code>build()</code> method of the <a href="https://docs.pydantic.dev/latest/api/networks/"><code>AnyUrl</code> and Dsn types</a>.</p> <p>This patch release also fixes an issue with the serialization of IP address types, when <code>serialize_as_any</code> is used. The next patch release will try to address the remaining issues with <em>serialize as any</em> behavior by introducing a new <em>polymorphic serialization</em> feature, that should be used in most cases in place of <em>serialize as any</em>.</p> <ul> <li> <p>Fix issue with forward references in parent <code>TypedDict</code> classes by <a href="https://github.com/Viicos"><code>@​Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12427">#12427</a>.</p> <p>This issue is only relevant on Python 3.14 and greater.</p> </li> <li> <p>Exclude fields with <code>exclude_if</code> from JSON Schema required fields by <a href="https://github.com/Viicos"><code>@​Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12430">#12430</a></p> </li> <li> <p>Revert URL percent-encoding of credentials in the <code>build()</code> method of the <a href="https://docs.pydantic.dev/latest/api/networks/"><code>AnyUrl</code> and Dsn types</a> by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1833">pydantic-core#1833</a>.</p> <p>This was initially considered as a bugfix, but caused regressions and as such was fully reverted. The next release will include an opt-in option to percent-encode components of the URL.</p> </li> <li> <p>Add type inference for IP address types by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1868">pydantic-core#1868</a>.</p> <p>The 2.12 changes to the <code>serialize_as_any</code> behavior made it so that IP address types could not properly serialize to JSON.</p> </li> <li> <p>Avoid getting default values from defaultdict by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1853">pydantic-core#1853</a>.</p> <p>This fixes a subtle regression in the validation behavior of the <a href="https://docs.python.org/3/library/collections.html#collections.defaultdict"><code>collections.defaultdict</code></a> type.</p> </li> <li> <p>Fix issue with field serializers on nested typed dictionaries by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1879">pydantic-core#1879</a>.</p> </li> <li> <p>Add more <code>pydantic-core</code> builds for the three-threaded version of Python 3.14 by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1864">pydantic-core#1864</a>.</p> </li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/pydantic/pydantic/compare/v2.12.3...v2.12.4">https://github.com/pydantic/pydantic/compare/v2.12.3...v2.12.4</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pydantic/pydantic/blob/v2.12.4/HISTORY.md">pydantic's changelog</a>.</em></p> <blockquote> <h2>v2.12.4 (2025-11-05)</h2> <p><a href="https://github.com/pydantic/pydantic/releases/tag/v2.12.4">GitHub release</a></p> <p>This is the fourth 2.12 patch release, fixing more regressions, and reverting a change in the <code>build()</code> method of the <a href="https://docs.pydantic.dev/latest/api/networks/"><code>AnyUrl</code> and Dsn types</a>.</p> <p>This patch release also fixes an issue with the serialization of IP address types, when <code>serialize_as_any</code> is used. The next patch release will try to address the remaining issues with <em>serialize as any</em> behavior by introducing a new <em>polymorphic serialization</em> feature, that should be used in most cases in place of <em>serialize as any</em>.</p> <ul> <li> <p>Fix issue with forward references in parent <code>TypedDict</code> classes by <a href="https://github.com/Viicos"><code>@​Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12427">#12427</a>.</p> <p>This issue is only relevant on Python 3.14 and greater.</p> </li> <li> <p>Exclude fields with <code>exclude_if</code> from JSON Schema required fields by <a href="https://github.com/Viicos"><code>@​Viicos</code></a> in <a href="https://redirect.github.com/pydantic/pydantic/pull/12430">#12430</a></p> </li> <li> <p>Revert URL percent-encoding of credentials in the <code>build()</code> method of the <a href="https://docs.pydantic.dev/latest/api/networks/"><code>AnyUrl</code> and Dsn types</a> by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1833">pydantic-core#1833</a>.</p> <p>This was initially considered as a bugfix, but caused regressions and as such was fully reverted. The next release will include an opt-in option to percent-encode components of the URL.</p> </li> <li> <p>Add type inference for IP address types by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1868">pydantic-core#1868</a>.</p> <p>The 2.12 changes to the <code>serialize_as_any</code> behavior made it so that IP address types could not properly serialize to JSON.</p> </li> <li> <p>Avoid getting default values from defaultdict by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1853">pydantic-core#1853</a>.</p> <p>This fixes a subtle regression in the validation behavior of the <a href="https://docs.python.org/3/library/collections.html#collections.defaultdict"><code>collections.defaultdict</code></a> type.</p> </li> <li> <p>Fix issue with field serializers on nested typed dictionaries by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1879">pydantic-core#1879</a>.</p> </li> <li> <p>Add more <code>pydantic-core</code> builds for the three-threaded version of Python 3.14 by <a href="https://github.com/davidhewitt"><code>@​davidhewitt</code></a> in <a href="https://redirect.github.com/pydantic/pydantic-core/pull/1864">pydantic-core#1864</a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="5c842dfc9c"><code>5c842df</code></a> Prepare release v2.12.4</li> <li><a href="c678a710e8"><code>c678a71</code></a> Bump <code>pydantic-core</code> to v2.41.5</li> <li><a href="a7cd29254b"><code>a7cd292</code></a> Bump <code>cloudpickle</code> to v3.1.2</li> <li><a href="21f627801b"><code>21f6278</code></a> Bump actions/setup-node from 5 to 6</li> <li><a href="8d6be8fea9"><code>8d6be8f</code></a> Bump astral-sh/setup-uv from 6 to 7</li> <li><a href="17865ea3a1"><code>17865ea</code></a> Bump actions/upload-artifact from 4 to 5</li> <li><a href="90ad0af6b9"><code>90ad0af</code></a> Bump actions/download-artifact from 5 to 6</li> <li><a href="18e6672b6f"><code>18e6672</code></a> Drop testing under PyPy 3.9</li> <li><a href="650215be2d"><code>650215b</code></a> Document workaround for <code>MongoDsn</code> default port</li> <li><a href="e326790227"><code>e326790</code></a> Fix example of for <code>bytes_invalid_encoding</code> validation error</li> <li>Additional commits viewable in <a href="https://github.com/pydantic/pydantic/compare/v2.12.3...v2.12.4">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-10 23:08:36 +00:00
Eric Eastwood	8fa7d4a5a3	Ignore Python language refactors (.git-blame-ignore-revs) (#19150) ... Ignore Python language refactors (`.git-blame-ignore-revs`) - https://github.com/element-hq/synapse/pull/19046 - https://github.com/element-hq/synapse/pull/19111 ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [x] Pull request is based on the develop branch * [x] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [x] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-11-10 22:34:30 +00:00
dependabot[bot]	a10e2386f1	Bump docker/metadata-action from 5.8.0 to 5.9.0 (#19161) ... Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5.8.0 to 5.9.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/docker/metadata-action/releases">docker/metadata-action's releases</a>.</em></p> <blockquote> <h2>v5.9.0</h2> <ul> <li>Add <code>tag-names</code> output to return tag names without image base name by <a href="https://github.com/crazy-max"><code>@​crazy-max</code></a> in <a href="https://redirect.github.com/docker/metadata-action/pull/553">docker/metadata-action#553</a></li> <li>Bump <code>@​babel/runtime-corejs3</code> from 7.14.7 to 7.28.2 in <a href="https://redirect.github.com/docker/metadata-action/pull/539">docker/metadata-action#539</a></li> <li>Bump <code>@​docker/actions-toolkit</code> from 0.62.1 to 0.66.0 in <a href="https://redirect.github.com/docker/metadata-action/pull/555">docker/metadata-action#555</a></li> <li>Bump brace-expansion from 1.1.11 to 1.1.12 in <a href="https://redirect.github.com/docker/metadata-action/pull/540">docker/metadata-action#540</a></li> <li>Bump csv-parse from 5.6.0 to 6.1.0 in <a href="https://redirect.github.com/docker/metadata-action/pull/532">docker/metadata-action#532</a></li> <li>Bump semver from 7.7.2 to 7.7.3 in in <a href="https://redirect.github.com/docker/metadata-action/pull/554">docker/metadata-action#554</a></li> <li>Bump tmp from 0.2.3 to 0.2.5 in <a href="https://redirect.github.com/docker/metadata-action/pull/541">docker/metadata-action#541</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/metadata-action/compare/v5.8.0...v5.9.0">https://github.com/docker/metadata-action/compare/v5.8.0...v5.9.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="318604b99e"><code>318604b</code></a> Merge pull request <a href="https://redirect.github.com/docker/metadata-action/issues/539">#539</a> from docker/dependabot/npm_and_yarn/babel/runtime-cor...</li> <li><a href="49c0a55d55"><code>49c0a55</code></a> chore: update generated content</li> <li><a href="486229e3f4"><code>486229e</code></a> Merge pull request <a href="https://redirect.github.com/docker/metadata-action/issues/558">#558</a> from crazy-max/fix-dist</li> <li><a href="f02aeab1ee"><code>f02aeab</code></a> chore: fix dist</li> <li><a href="beafb97305"><code>beafb97</code></a> chore(deps): Bump <code>@​babel/runtime-corejs3</code> from 7.14.7 to 7.28.2</li> <li><a href="3ff819c6c5"><code>3ff819c</code></a> Merge pull request <a href="https://redirect.github.com/docker/metadata-action/issues/557">#557</a> from crazy-max/yarn-4.9.2</li> <li><a href="05838e9769"><code>05838e9</code></a> update yarn to 4.9.2</li> <li><a href="43fa4ac0d3"><code>43fa4ac</code></a> Merge pull request <a href="https://redirect.github.com/docker/metadata-action/issues/556">#556</a> from crazy-max/dev-deps</li> <li><a href="b3120f2f18"><code>b3120f2</code></a> chore: update generated content</li> <li><a href="1f469d21ee"><code>1f469d2</code></a> update dev dependencies</li> <li>Additional commits viewable in <a href="c1e51972af...318604b99e">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-10 22:26:59 +00:00
dependabot[bot]	674b932b33	Bump sentry-sdk from 2.34.1 to 2.43.0 (#19157) ... Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 2.34.1 to 2.43.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-python/releases">sentry-sdk's releases</a>.</em></p> <blockquote> <h2>2.43.0</h2> <h3>Various fixes &amp; improvements</h3> <ul> <li> <p>Pydantic AI integration (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4906">#4906</a>) by <a href="https://github.com/constantinius"><code>@​constantinius</code></a></p> <p>Enable the new Pydantic AI integration with the code snippet below, and you can use the Sentry AI dashboards to observe your AI calls:</p> <pre lang="python"><code>import sentry_sdk from sentry_sdk.integrations.pydantic_ai import PydanticAIIntegration sentry_sdk.init( dsn=&quot;&lt;your-dsn&gt;&quot;, # Set traces_sample_rate to 1.0 to capture 100% # of transactions for tracing. traces_sample_rate=1.0, # Add data like inputs and responses; # see https://docs.sentry.io/platforms/python/data-management/data-collected/ for more info send_default_pii=True, integrations=[ PydanticAIIntegration(), ], ) </code></pre> </li> <li> <p>MCP Python SDK (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4964">#4964</a>) by <a href="https://github.com/constantinius"><code>@​constantinius</code></a></p> <p>Enable the new Python MCP integration with the code snippet below:</p> <pre lang="python"><code>import sentry_sdk from sentry_sdk.integrations.mcp import MCPIntegration sentry_sdk.init( dsn=&quot;&lt;your-dsn&gt;&quot;, # Set traces_sample_rate to 1.0 to capture 100% # of transactions for tracing. traces_sample_rate=1.0, # Add data like inputs and responses; # see https://docs.sentry.io/platforms/python/data-management/data-collected/ for more info send_default_pii=True, integrations=[ MCPIntegration(), ], ) </code></pre> </li> <li> <p>fix(strawberry): Remove autodetection, always use sync extension (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4984">#4984</a>) by <a href="https://github.com/sentrivana"><code>@​sentrivana</code></a></p> <p>Previously, <code>StrawberryIntegration</code> would try to guess whether it should install the sync or async version of itself. This auto-detection was very brittle and could lead to us auto-enabling async code in a sync context. With this change, <code>StrawberryIntegration</code> remains an auto-enabling integration, but it'll enable the sync version by default. If you want to enable the async version, pass the option explicitly:</p> <pre lang="python"><code>sentry_sdk.init( # ... </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md">sentry-sdk's changelog</a>.</em></p> <blockquote> <h2>2.43.0</h2> <h3>Various fixes &amp; improvements</h3> <ul> <li> <p>Pydantic AI integration (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4906">#4906</a>) by <a href="https://github.com/constantinius"><code>@​constantinius</code></a></p> <p>Enable the new Pydantic AI integration with the code snippet below, and you can use the Sentry AI dashboards to observe your AI calls:</p> <pre lang="python"><code>import sentry_sdk from sentry_sdk.integrations.pydantic_ai import PydanticAIIntegration sentry_sdk.init( dsn=&quot;&lt;your-dsn&gt;&quot;, # Set traces_sample_rate to 1.0 to capture 100% # of transactions for tracing. traces_sample_rate=1.0, # Add data like inputs and responses; # see https://docs.sentry.io/platforms/python/data-management/data-collected/ for more info send_default_pii=True, integrations=[ PydanticAIIntegration(), ], ) </code></pre> </li> <li> <p>MCP Python SDK (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4964">#4964</a>) by <a href="https://github.com/constantinius"><code>@​constantinius</code></a></p> <p>Enable the new Python MCP integration with the code snippet below:</p> <pre lang="python"><code>import sentry_sdk from sentry_sdk.integrations.mcp import MCPIntegration sentry_sdk.init( dsn=&quot;&lt;your-dsn&gt;&quot;, # Set traces_sample_rate to 1.0 to capture 100% # of transactions for tracing. traces_sample_rate=1.0, # Add data like inputs and responses; # see https://docs.sentry.io/platforms/python/data-management/data-collected/ for more info send_default_pii=True, integrations=[ MCPIntegration(), ], ) </code></pre> </li> <li> <p>fix(strawberry): Remove autodetection, always use sync extension (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4984">#4984</a>) by <a href="https://github.com/sentrivana"><code>@​sentrivana</code></a></p> <p>Previously, <code>StrawberryIntegration</code> would try to guess whether it should install the sync or async version of itself. This auto-detection was very brittle and could lead to us auto-enabling async code in a sync context. With this change, <code>StrawberryIntegration</code> remains an auto-enabling integration, but it'll enable the sync version by default. If you want to enable the async version, pass the option explicitly:</p> <pre lang="python"><code>sentry_sdk.init( </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="b069aa24fd"><code>b069aa2</code></a> Update CHANGELOG.md</li> <li><a href="a7a3fb1795"><code>a7a3fb1</code></a> release: 2.43.0</li> <li><a href="76cc416308"><code>76cc416</code></a> fix(google-genai): Set agent name (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5038">#5038</a>)</li> <li><a href="b3b2eb62d9"><code>b3b2eb6</code></a> fix(integrations): hooking into error tracing function to find out if an exec...</li> <li><a href="d7ccf06aea"><code>d7ccf06</code></a> fix(django): Improve logic for classifying cache hits and misses (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5029">#5029</a>)</li> <li><a href="64c145ffb1"><code>64c145f</code></a> chore(metrics): Rename _metrics to metrics (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5035">#5035</a>)</li> <li><a href="fe31660c50"><code>fe31660</code></a> fix(tracemetrics): Bump metric buffer size to 1k (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5031">#5031</a>)</li> <li><a href="6e06a07467"><code>6e06a07</code></a> fix startlette deprecation warning (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5034">#5034</a>)</li> <li><a href="e6366194f6"><code>e636619</code></a> fix(strawberry): Remove autodetection, always use sync extension (<a href="https://redirect.github.com/getsentry/sentry-python/issues/4984">#4984</a>)</li> <li><a href="8ab8f3b389"><code>8ab8f3b</code></a> ci: 🤖 Update test matrix with new releases (10/27) (<a href="https://redirect.github.com/getsentry/sentry-python/issues/5033">#5033</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-python/compare/2.34.1...2.43.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-10 22:24:27 +00:00
V02460	dc7f01f334	register_new_matrix_user: Support multiple config files (#18784) ... Co-authored-by: Andrew Morgan <andrew@amorgan.xyz>	2025-11-10 16:52:57 +00:00
reivilibre	a50923b6bf	Improve documentation around streams, particularly ID generators and adding new streams. (#18943) ... This arises mostly from my recent experience adding a stream for Thread Subscriptions and trying to help others add their own streams. --------- Signed-off-by: Olivier 'reivilibre <oliverw@matrix.org>	2025-11-10 13:07:22 +00:00
Sharakea	378c5c838c	Document Nginx Proxy Manager configuration steps (#19136) ... Added configuration details for Nginx Proxy Manager including proxy host setup, SSL/TLS settings, and advanced configurations for change the Federation Port.	2025-11-10 13:05:45 +00:00
Andrew Morgan	39f8e28861	Update cibuildwheel config to stop building Python 3.9 and free-threaded wheels (#19154)	2025-11-10 13:05:03 +00:00
Andrew Ferrazzutti	8580ab60c9	Add delayed_events table to boolean column port (#19155) ... The `delayed_events` table has a boolean column that should be handled by the SQLite->PostgreSQL migration script.	2025-11-10 12:17:42 +00:00
Andrew Morgan	077a6f7e63	Merge branch 'release-v1.142' into develop	2025-11-07 12:09:02 +00:00
Andrew Morgan	72073d82ae	Move important messages to the top of the changelog	2025-11-07 11:20:20 +00:00
Andrew Morgan	5d4a731499	1.142.0rc4	2025-11-07 10:54:55 +00:00
Andrew Morgan	18f1d28a49	1.142.0rc1 regression fix: Allow coercing a str to a FilePath in MasConfigModel (#19144)	2025-11-07 10:41:05 +00:00
Andrew Ferrazzutti	fcac7e0282	Write union types as X | Y where possible (#19111) ... aka PEP 604, added in Python 3.10	2025-11-06 14:02:33 -06:00
Erik Johnston	6790312831	Fixup logcontexts after replication PR. (#19146) ... Fixes logcontext leaks introduced in #19138.	2025-11-05 15:38:14 +00:00
Erik Johnston	d3ffd04f66	Fix spelling (#19145) ... Fixes up #19138	2025-11-05 14:00:59 +00:00
Erik Johnston	4906771da1	Faster redis replication handling (#19138) ... Spawning a background process comes with a bunch of overhead, so let's try to reduce the number of background processes we need to spawn when handling inbound fed. Currently, we seem to be doing roughly one per command. Instead, lets keep the background process alive for a bit waiting for a new command to come in.	2025-11-05 13:42:04 +00:00
Andrew Morgan	2fd8d88b42	1.142.0rc3	2025-11-04 17:39:28 +00:00
Andrew Morgan	0cbb2a15e0	Don't build free-threaded wheels (#19140) ... Fixes https://github.com/element-hq/synapse/issues/19139.	2025-11-04 17:38:25 +00:00
Andrew Morgan	5d71034f81	1.142.0rc2	2025-11-04 16:21:50 +00:00
Andrew Morgan	4bbde142dc	Skip building Python 3.9 wheels with cibuildwheel (#19119)	2025-11-04 16:20:01 +00:00
Andrew Morgan	d888126372	Drop period from title	2025-11-04 14:05:51 +00:00
Andrew Morgan	b2237ff4f1	Add sqlite deprecation to changelog and upgrade notes	2025-11-04 13:40:58 +00:00
Andrew Morgan	2760d15348	1.142.0rc1	2025-11-04 13:34:46 +00:00
Erik Johnston	5408101d21	Speed up pruning of ratelimiter (#19129) ... I noticed this in some profiling. Basically, we prune the ratelimiters by copying and iterating over every entry every 60 seconds. Instead, let's use a wheel timer to track when we should potentially prune a given key, and then we a) check fewer keys, and b) can run more frequently. Hopefully this should mean we don't have a large pause everytime we prune a ratelimiter with lots of keys. Also fixes a bug where we didn't prune entries that were added via `record_action` and never subsequently updated. This affected the media and joins-per-room ratelimiter.	2025-11-04 12:44:57 +00:00
Andrew Morgan	08f570f5f5	Fix "There is no current event loop in thread" error in tests (#19134)	2025-11-04 12:32:49 +00:00
Eric Eastwood	db00925ae7	Redirect stdout/stderr to logs after initialization (#19131) ... This regressed in https://github.com/element-hq/synapse/pull/19121. I moved things in https://github.com/element-hq/synapse/pull/19121 because I thought that it made sense to redirect anything printed to `stdout`/`stderr` to the logs as early as possible. But we actually want to log any immediately apparent problems during initialization to `stderr` in the terminal so that they are obvious and visible to the operator. Now, I've moved `redirect_stdio_to_logs()` back to where it was previously along with some proper comment context for why we have it there.	2025-11-03 16:16:23 -06:00
Eric Eastwood	891acfd502	Move oidc.load_metadata() startup into _base.start() (#19056) ... Slightly related to ["clean-tenant provisioning"](https://github.com/element-hq/synapse-small-hosts/issues/221) as making startup cleaner, makes it more clear how to handle clean provisioning.	2025-11-03 15:23:22 -06:00
Eric Eastwood	e02a6f5e5d	Fix lost logcontext on HomeServer.shutdown() (#19108) ... Same fix as https://github.com/element-hq/synapse/pull/19090 Spawning from working on clean tenant deprovisioning in the Synapse Pro for small hosts project (https://github.com/element-hq/synapse-small-hosts/pull/204).	2025-11-03 14:07:10 -06:00
dependabot[bot]	4f9dc3b613	Bump psycopg2 from 2.9.10 to 2.9.11 (#19125) ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-03 19:19:06 +00:00
dependabot[bot]	2c5deb800e	Bump icu_segmenter from 2.0.0 to 2.0.1 (#19126) ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-03 19:18:16 +00:00
Eric Eastwood	a7107458c6	Refactor app entrypoints (avoid exit(1) in our composable functions) (#19121) ... - Move `register_start` (calls `os._exit(1)`) out of `setup` (our composable function) - We want to avoid `exit(...)` because we use these composable functions in Synapse Pro for small hosts where we have multiple Synapse instances running in the same process. We don't want a problem from one homeserver tenant causing the entire Python process to exit and affect all of the other homeserver tenants. - Continuation of https://github.com/element-hq/synapse/pull/19116 - Align our app entrypoints: `homeserver` (main), `generic_worker` (worker), and `admin_cmd` ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process) (c.f Synapse Pro for small hosts), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Clean tenant provisioning" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/48	2025-11-03 12:04:43 -06:00
dependabot[bot]	f02ac5a4d5	Bump markdown-it-py from 3.0.0 to 4.0.0 (#19123) ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-03 17:19:20 +00:00
Eric Eastwood	e00a411837	Move exception handling up the stack (avoid exit(1) in our composable functions) (#19116) ... Move exception handling up the stack (avoid `exit(1)` in our composable functions) Relevant to Synapse Pro for small hosts as we don't want to exit the entire Python process and affect all homeserver tenants. ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process) (c.f Synapse Pro for small hosts), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Clean tenant provisioning" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/48	2025-11-03 11:18:56 -06:00
dependabot[bot]	bc926bd99e	Bump ruff from 0.12.10 to 0.14.3 (#19124) ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-11-03 16:38:19 +00:00
Andrew Morgan	69bab78b44	Python 3.14 support (#19055) ... Co-authored-by: Eric Eastwood <erice@element.io>	2025-11-03 11:53:59 +00:00
Eric Eastwood	41a2762e58	Be mindful of other logging context filters in 3rd-party code (#19068) ... Be mindful that Synapse can be run alongside other code in the same Python process. We shouldn't overwrite fields on given log record unless we know it's relevant to Synapse. (no clobber) ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Per-tenant logging" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/48	2025-10-31 10:12:05 -05:00
Erik Johnston	3ccc5184e0	Fix schema lint script to understand CREATE TABLE IF NOT EXISTS (#19020) ... The schema lint tries to make sure we don't add or remove indices in schema files (rather than as background updates), *unless* the table was created in the same schema file. The regex to pull out the `CREATE TABLE` SQL incorrectly didn't recognise `IF NOT EXISTS`. There is a test delta file that shows that we accept different types of `CREATE TABLE` and `CREATE INDEX` statements, as well as an index creation that doesn't have a matching create table (to show that we do still catch it). The test delta should be removed before merge.	2025-10-31 13:16:47 +00:00
V02460	07e7980572	Fix Rust’s confusing lifetime lint (#19118) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-10-31 12:09:13 +00:00
V02460	3595ff921f	Pydantic v2 (#19071) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by: Andrew Morgan <andrew@amorgan.xyz>	2025-10-31 09:22:22 +00:00
Andrew Morgan	300c5558ab	Update check_dependencies to support markers (#19110)	2025-10-30 21:33:29 +00:00
Eric Eastwood	c0b9437ab6	Fix lost logcontext when using timeout_deferred(...) (#19090) ... Fix lost logcontext when using `timeout_deferred(...)` and things actually timeout. Fix https://github.com/element-hq/synapse/issues/19087 (our HTTP client times out requests using `timeout_deferred(...)` Fix https://github.com/element-hq/synapse/issues/19066 (`/sync` uses `notifier.wait_for_events()` which uses `timeout_deferred(...)` under the hood) ### When/why did these lost logcontext warnings start happening? ``` synapse.logging.context - 107 - WARNING - sentinel - Expected logging context call_later but found POST-2453 synapse.logging.context - 107 - WARNING - sentinel - Expected logging context call_later was lost ``` In https://github.com/element-hq/synapse/pull/18828, we switched `timeout_deferred(...)` from using `reactor.callLater(...)` to [`clock.call_later(...)`](3b59ac3b69/synapse/util/clock.py (L224-L313)) under the hood. This meant it started dealing with logcontexts but our `time_it_out()` callback didn't follow our [Synapse logcontext rules](3b59ac3b69/docs/log_contexts.md).	2025-10-30 11:49:15 -05:00
Eric Eastwood	f0aae62f85	Cheaper logcontext debug logs (random_string_insecure_fast(...)) (#19094) ... Follow-up to https://github.com/element-hq/synapse/pull/18966 During the weekly Backend team meeting, it was mentioned that `random_string(...)` was taking a significant amount of CPU on `matrix.org`. This makes sense as it relies on [`secrets.choice(...)`](https://docs.python.org/3/library/secrets.html#secrets.choice), a cryptographically secure function that is inherently computationally expensive. And since https://github.com/element-hq/synapse/pull/18966, we're calling `random_string(...)` as part of a bunch of logcontext utilities. Since we don't need cryptographically secure random strings for our debug logs, this PR is introducing a new `random_string_insecure_fast(...)` function that uses [`random.choice(...)`](https://docs.python.org/3/library/random.html#random.choice) which uses pseudo-random numbers that are "both fast and threadsafe".	2025-10-30 11:47:53 -05:00
Andrew Morgan	349599143e	Move reading of multipart response into try body (#19062)	2025-10-30 15:22:52 +00:00
Eric Eastwood	2c4057bf93	Prevent duplicate logging setup when running multiple Synapse instances (#19067) ... Be mindful that it's possible to run Synapse multiple times in the same Python process. So we only need to do some part of the logging setup once. - We only need to setup the global log record factory and context filter once - We only need to redirect Twisted logging once ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Per-tenant logging" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/48	2025-10-30 10:21:56 -05:00
Andrew Morgan	f54ddbcace	Prevent duplicate GH releases being created during Synapse release process (#19096)	2025-10-30 12:40:53 +00:00
Andrew Morgan	728512918e	Exclude .lock file from /usr/local when building docker images (#19107)	2025-10-30 10:17:35 +00:00
Andrew Ferrazzutti	e0838c2567	Drop Python 3.9, bump tests/builds to Python 3.10 (#19099) ... Python 3.9 EOL is on 2025-10-31	2025-10-29 12:15:00 -05:00
dependabot[bot]	32998d07d2	Bump sigstore/cosign-installer from 3.10.0 to 4.0.0 (#19075) ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2025-10-29 15:39:07 +00:00