This is an automated email from the ASF dual-hosted git repository.

damccorm pushed a commit to branch users/damccorm/depUpdates
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/users/damccorm/depUpdates by 
this push:
     new aa1916bde73 Update release-guide.md
aa1916bde73 is described below

commit aa1916bde73ed0a86f650ec5cfa95d025c0a24c9
Author: Danny McCormick <[email protected]>
AuthorDate: Thu Apr 11 19:28:50 2024 -0400

    Update release-guide.md
---
 contributor-docs/release-guide.md | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/contributor-docs/release-guide.md 
b/contributor-docs/release-guide.md
index f1d91a295bf..16d58bd966e 100644
--- a/contributor-docs/release-guide.md
+++ b/contributor-docs/release-guide.md
@@ -239,17 +239,6 @@ releases to the Maven Central Repository.
 
 Each language has routine dependency maintenance that you should check now.
 
-#### Update base image dependencies for Python container images
-
-The Python base container images have pinned `requirements.txt` that are
-compatible with our dependency constraints, and design to avoid run-time
-installs, since run-time installs cause large delays at start-up time. Ideally,
-we this should happen regularly when dependencies update, but it is important
-to ensure that they are fully up to date for each release.
-
-Follow the instructions at
-https://s.apache.org/beam-python-requirements-generate
-
 #### Update Go version used for container builds
 
 Go makes security patch releases of their tooling.  This potentially affects
@@ -1331,6 +1320,15 @@ Release Manager
 [1] https://github.com/apache/beam/pull/123
 ```
 
+#### Update Python Dependencies
+
+A PR should have already been created (and possibly merged) by github-actions 
bot, you should verify that this was done correctly
+by looking at open PRs from that bot - 
https://github.com/apache/beam/pulls/app%2Fgithub-actions
+
+If a PR has not been merged, drive it to completion.
+If no PR was created, triage any failures in 
https://github.com/apache/beam/actions/workflows/beam_Publish_Website.yml and 
manually regenerate dependencies,
+following 
https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-HowtoupdatedependenciesthatareinstalledinPythoncontainerimages
+
 ### Update the Java starter repo
 
 After the new Beam release is published, the Java starter project needs to 
have its version manually upgraded.

Reply via email to