[BEAM-4767] Remove beam- prefix from release script tags#16899
[BEAM-4767] Remove beam- prefix from release script tags#16899emilymye merged 2 commits intoapache:masterfrom
Conversation
TheNeuralBit
left a comment
There was a problem hiding this comment.
This LGTM, but I just have a couple questions. It looks like tagging the RC drops the beam-, but just for the fnapi container: 6adfaca#diff-8f2f682def71854816cc757228ece9384fcc753fd338a19dcf2a5b3ccca92185
- Any chance this will break the logic in the RC tagging script?
- Is it correct to update both, or should the legacy one still be
beam-2.xx.x?
|
I'll change the cut RC, but see gcr.io/cloud-dataflow/v1beta3/beam_java8_sdk:2.36.0and gcr.io/cloud-dataflow/v1beta3/beam-java-batch:2.36.0 vs gcr.io/cloud-dataflow/v1beta3/beam-java-batch:beam-2.36.0 legacy version that doesn't not exist) |
Codecov Report
@@ Coverage Diff @@
## master #16899 +/- ##
==========================================
+ Coverage 74.65% 83.60% +8.95%
==========================================
Files 656 452 -204
Lines 82424 62302 -20122
==========================================
- Hits 61532 52088 -9444
+ Misses 19892 10214 -9678
+ Partials 1000 0 -1000
Continue to review full report at Codecov.
|
Confirmed, diff for a release branch for 2.37.0 would look like:
R: @TheNeuralBit
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.