dependabot[bot] opened a new pull request, #41: URL: https://github.com/apache/beam-starter-go/pull/41
Bumps [github.com/apache/beam/sdks/v2](https://github.com/apache/beam) from 2.58.0 to 2.58.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/apache/beam/releases";>github.com/apache/beam/sdks/v2's releases</a>.</em></p> <blockquote> <h2>Beam 2.58.1 release</h2> <p>We are happy to present the new 2.58.1 release of Beam. This release includes both improvements and new functionality. See the <a href="https://github.com/apache/beam/blob/HEAD/get-started/downloads/#2580-2024-08-06";>download page</a> for this release.</p> <!-- raw HTML omitted --> <h2>New Features / Improvements</h2> <ul> <li>Fixed issue where KafkaIO Records read with <code>ReadFromKafkaViaSDF</code> are redistributed and may contain duplicates regardless of the configuration. This affects Java pipelines with Dataflow v2 runner and xlang pipelines reading from Kafka, (<a href="https://redirect.github.com/apache/beam/issues/32196";>#32196</a>)</li> </ul> <h2>Known Issues</h2> <ul> <li>Large Dataflow graphs using runner v2, or pipelines explicitly enabling the <code>upload_graph</code> experiment, will fail at construction time (<a href="https://redirect.github.com/apache/beam/issues/32159";>#32159</a>).</li> <li>Python pipelines that run with 2.53.0-2.58.0 SDKs and read data from GCS might be affected by a data corruption issue (<a href="https://redirect.github.com/apache/beam/issues/32169";>#32169</a>). The issue will be fixed in 2.59.0 (<a href="https://redirect.github.com/apache/beam/pull/32135";>#32135</a>). To work around this, update the google-cloud-storage package to version 2.18.2 or newer.</li> </ul> <p>For the most up to date list of known issues, see <a href="https://github.com/apache/beam/blob/master/CHANGES.md";>https://github.com/apache/beam/blob/master/CHANGES.md</a></p> <h2>List of Contributors</h2> <p>According to git shortlog, the following people contributed to the 2.58.1 release. Thank you to all contributors!</p> <p>Danny McCormick</p> <p>Sam Whittle</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/apache/beam/blob/master/CHANGES.md";>github.com/apache/beam/sdks/v2's changelog</a>.</em></p> <blockquote> <h1>[2.58.1] - 2024-08-15</h1> <h2>New Features / Improvements</h2> <ul> <li>Fixed issue where KafkaIO Records read with <code>ReadFromKafkaViaSDF</code> are redistributed and may contain duplicates regardless of the configuration. This affects Java pipelines with Dataflow v2 runner and xlang pipelines reading from Kafka, (<a href="https://redirect.github.com/apache/beam/issues/32196";>#32196</a>)</li> </ul> <h2>Known Issues</h2> <ul> <li>Large Dataflow graphs using runner v2, or pipelines explicitly enabling the <code>upload_graph</code> experiment, will fail at construction time (<a href="https://redirect.github.com/apache/beam/issues/32159";>#32159</a>).</li> <li>Python pipelines that run with 2.53.0-2.58.0 SDKs and read data from GCS might be affected by a data corruption issue (<a href="https://redirect.github.com/apache/beam/issues/32169";>#32169</a>). The issue will be fixed in 2.59.0 (<a href="https://redirect.github.com/apache/beam/pull/32135";>#32135</a>). To work around this, update the google-cloud-storage package to version 2.18.2 or newer.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/apache/beam/commit/414bc202dbafbc699e8e590e60004d52ddca105f";><code>414bc20</code></a> Set version for 2.58.1 RC1</li> <li><a href="https://github.com/apache/beam/commit/57e5a46300c8833d4604291bb92003bc656e4186";><code>57e5a46</code></a> Cherry pick (<a href="https://redirect.github.com/apache/beam/issues/32202";>#32202</a>)</li> <li><a href="https://github.com/apache/beam/commit/5e697235bcd7c5de5c3662a8e05b1146b5ad5fad";><code>5e69723</code></a> Update dataflow container versions (<a href="https://redirect.github.com/apache/beam/issues/32203";>#32203</a>)</li> <li>See full diff in <a href="https://github.com/apache/beam/compare/v2.58.0...v2.58.1";>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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
