Skip to content

Conversation

@chewy-zlai
Copy link
Collaborator

@chewy-zlai chewy-zlai commented Mar 14, 2025

Summary

This workflow is triggered when someone creates a new Release on Github. It first checks to see if the integration tests have passed for the current commit in main. If not it will convert the Release to a draft. If the tests passed, it copies the candidate version of the jars and wheel from the canary buckets and distributes them to all of the customer cloud buckets.

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

  • New Features

    • Introduced an automated release process to streamline publication workflows and ensure consistent artifact handling.
  • Documentation

    • Updated release instructions with clearer guidance on version tagging and release creation options via both CLI and UI, while condensing the explanation of the release command's functionality.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (3)
.github/workflows/publish_release.yaml (3)

161-165: Standardize condition quoting.
Use double quotes for the ${{ github.event.release.isLatest }} variable in all if conditions.

Also applies to: 169-169, 177-179, 184-184, 284-285, 290-291


59-59: Remove trailing spaces.
Eliminate extra whitespace on these lines.

Also applies to: 174-174, 177-177, 180-181, 184-184, 280-280

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 59-59: trailing spaces

(trailing-spaces)


256-256: Fix indentation.
Correct the indentation to the expected 6 spaces.

🧰 Tools
🪛 YAMLlint (1.35.1)

[warning] 256-256: wrong indentation: expected 6 but found 8

(indentation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 8101be6 and b7962f3.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 59-59: trailing spaces

(trailing-spaces)


[error] 174-174: trailing spaces

(trailing-spaces)


[error] 177-177: trailing spaces

(trailing-spaces)


[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)


[warning] 256-256: wrong indentation: expected 6 but found 8

(indentation)


[error] 280-280: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_python_wheel
  • GitHub Check: enforce_triggered_workflows

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
.github/workflows/publish_release.yaml (4)

161-165: Fix quoting in if condition
Change single quotes to double quotes for ${{ github.event.release.isLatest }}.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

169-173: Fix quoting in if condition
Change single quotes to double quotes for ${{ github.event.release.isLatest }}.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

284-287: Fix quoting in AWS if conditions
Replace single quotes with double quotes for ${{ github.event.release.isLatest }} in the AWS upload blocks.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

Also applies to: 290-296


180-184: Remove trailing spaces
Clean up extra whitespace to satisfy YAML lint.

Also applies to: 280-280

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between b7962f3 and 499120f.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)


[error] 280-280: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_python_wheel
  • GitHub Check: enforce_triggered_workflows

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
.github/workflows/publish_release.yaml (3)

55-55: Quote var: Wrap ${{ steps.get_sha.outputs.latest_sha }} in quotes in the if-condition.


180-184: Clean spcs: Remove trailing spaces.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)


276-276: Clean spcs: Remove trailing spaces.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 276-276: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 499120f and 1b685f5.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)


[error] 276-276: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_python_wheel
  • GitHub Check: enforce_triggered_workflows
🔇 Additional comments (2)
.github/workflows/publish_release.yaml (2)

161-172: Quote if: Use double quotes for ${{ github.event.release.isLatest }} in conditionals.


280-292: Quote if: Use double quotes for ${{ github.event.release.isLatest }} in conditionals.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (9)
.github/workflows/publish_release.yaml (9)

7-9: 🛠️ Refactor suggestion

Dynamic VERSION: Replace the static "v0.0.0" with a dynamic tag.

-  VERSION: "v0.0.0"
+  VERSION: "${{ github.event.release.tag_name }}"

169-172: 🛠️ Refactor suggestion

GCS If Condition: Update to double quotes for proper interpolation.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

286-288: 🛠️ Refactor suggestion

AWS If Condition: Update quotes for consistency.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

290-292: 🛠️ Refactor suggestion

AWS If Condition: Use double quotes instead.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

280-283: 🛠️ Refactor suggestion

AWS If Condition: Change to double quotes for proper evaluation.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

294-296: 🛠️ Refactor suggestion

AWS If Condition: Replace single quotes with double quotes.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

161-165: 🛠️ Refactor suggestion

GCS If Condition: Use double quotes for the condition.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

176-179: 🛠️ Refactor suggestion

GCS If Condition: Replace single with double quotes.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then

182-185: 🛠️ Refactor suggestion

GCS If Condition: Use double quotes in the if-statement.

-if [ '${{ github.event.release.isLatest }}' == 'true' ]; then
+if [ "${{ github.event.release.isLatest }}" == "true" ]; then
🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 184-184: trailing spaces

(trailing-spaces)

🧹 Nitpick comments (4)
.github/workflows/publish_release.yaml (4)

85-98: Thrift Installation: Consider adding the -y flag to apt-get install.


180-181: Trailing Spaces: Remove trailing spaces.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


184-184: Trailing Space: Remove the extra space.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 184-184: trailing spaces

(trailing-spaces)


276-276: Trailing Space: Remove the trailing whitespace.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 276-276: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 1b685f5 and 186a01f.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 180-180: trailing spaces

(trailing-spaces)


[error] 181-181: trailing spaces

(trailing-spaces)


[error] 184-184: trailing spaces

(trailing-spaces)


[error] 276-276: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_python_wheel
  • GitHub Check: enforce_triggered_workflows
🔇 Additional comments (23)
.github/workflows/publish_release.yaml (23)

11-21: CI Check Job: Steps and permissions look correct.


22-27: Branch SHA Retrieval: The SHA extraction is concise.


28-38: Run ID Extraction: Retrieval of the push-to-canary run ID is clear.


40-46: Artifact Download: The artifact is downloaded as expected.


47-59: CI Status Check: Verification logic is solid.


60-68: Draft Conversion: The draft conversion step is correctly implemented.


69-84: Build Job Setup: Checkout and Python setup are properly configured.


99-111: Build Script: Wheel building and file verification are correct.


112-117: Artifact Upload: Upload step for the wheel artifact is fine.


118-120: Job Outputs: The output mapping is appropriate.


121-147: GCP Job Setup: Repository checkout, GCP authentication, and artifact download are set up correctly.


190-197: Attach Wheel: The wheel upload command is correctly configured.


198-204: Attach Flink Assembly Jar: The step is properly set up.


206-212: Attach Cloud GCP Jar: This step is implemented as expected.


213-219: Attach Service Assembly Jar: The command correctly attaches the jar.


220-230: JFrog CLI Setup: Configuration and setup steps are clear.


231-246: Artifactory Uploads: All upload commands for artifacts are in order.


247-269: AWS Job Setup: Checkout, AWS credentials, and artifact download are fine.


299-305: Attach Cloud AWS Jar: The release upload step is correct.


307-311: JFrog CLI (AWS): Setup is properly configured.


312-318: JFrog CLI Config: The configuration with the access token is clear.


319-322: AWS Artifactory Upload: Upload command for AWS jar is correctly defined.


323-337: Cleanup Artifacts: The artifact deletion step is implemented correctly.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
.github/workflows/publish_release.yaml (5)

52-56: Quote CI SHA.
Consider quoting ${{ steps.get_sha.outputs.latest_sha }} to prevent word splitting.


155-184: Quote isLatest in conditions.
Prefer using double quotes in if conditions (e.g. if [ "${{ github.event.release.isLatest }}" == "true" ]; then) to avoid shell pitfalls.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 178-178: trailing spaces

(trailing-spaces)


[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


178-182: Remove trailing spaces.
Trailing whitespace detected—please remove them.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 178-178: trailing spaces

(trailing-spaces)


[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


267-289: Improve shell quoting.
Use double quotes for ${{ github.event.release.isLatest }} comparisons in AWS steps.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 270-270: trailing spaces

(trailing-spaces)


270-270: Remove trailing space.
Trailing whitespace at this line; please clean up.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 270-270: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 186a01f and 3f91f70.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 178-178: trailing spaces

(trailing-spaces)


[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


[error] 270-270: trailing spaces

(trailing-spaces)

🔇 Additional comments (13)
.github/workflows/publish_release.yaml (13)

1-5: Workflow trigger defined.
The workflow’s trigger and name are clear.


6-7: Environment block OK.
VERSION is set dynamically from the release tag.


15-25: Checkout & SHA retrieval.
Good use of checkout and capturing the latest SHA.


26-37: Run ID acquisition.
The logic retrieves a successful run ID and fails early if absent.


38-44: CI Artifact download.
Artifact download step is straightforward.


58-66: Draft conversion on failure.
Correct fallback if CI check fails.


72-109: Wheel build job.
Build steps (checkout, Python setup, Thrift install, and wheel build) look solid.


110-115: Artifact upload step.
The wheel artifact is uploaded as expected.


188-212: Release attachment steps.
All release artifact upload commands for wheel and jars are clear.


213-239: JFrog CLI integration.
JFrog setup and upload steps are well structured.


292-297: AWS release attachment.
The attachment of the Cloud AWS Jar is implemented correctly.


298-315: JFrog setup for AWS.
The AWS JFrog CLI configuration and upload steps are clear.


316-329: Cleanup job.
The deletion of artifacts is simple and effective.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
.github/workflows/publish_release.yaml (3)

53-56: Quote Dynamic Value.
Quote the expression for ${{ steps.get_sha.outputs.latest_sha }} to avoid any word splitting.


178-182: Remove Trailing Spaces.
Trailing whitespace detected on these lines. Please remove it for cleaner formatting.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 178-178: trailing spaces

(trailing-spaces)


[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


269-270: Remove Trailing Spaces.
Trailing whitespace is present here; please clean it up.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 270-270: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 3f91f70 and cf98367.

📒 Files selected for processing (1)
  • .github/workflows/publish_release.yaml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 178-178: trailing spaces

(trailing-spaces)


[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


[error] 270-270: trailing spaces

(trailing-spaces)

🔇 Additional comments (11)
.github/workflows/publish_release.yaml (11)

1-5: Workflow Trigger OK.
Name and release event trigger are set up correctly.


6-7: Dynamic VERSION Set.
Injecting the release tag as VERSION is correct.


9-67: CI Check Job OK.
The steps to verify the commit SHA and to convert the release to draft if needed are clear.


83-109: Wheel Build Job OK.
Version substitution using ${VERSION#v} is handled properly; please test with various tag formats.


119-177: GCP Promotion Steps OK.
Artifact uploads and metadata updates are comprehensive and clear.


188-240: Release Attachments & JFrog Setup OK.
Attaching artifacts and configuring JFrog CLI are correctly implemented.


241-263: AWS Promotion Steps OK.
The AWS job mirrors the GCP flow well; ensure S3 metadata and permissions are as expected.


271-291: AWS Artifact Loop OK.
Loop logic for uploading the wheel and jars to different S3 buckets is sound.


293-297: AWS Release Attachment OK.
The release attachment step uses the dynamic version correctly.


299-315: JFrog CLI AWS Upload OK.
JFrog CLI configuration and upload commands are implemented properly.


316-329: Cleanup Job OK.
Artifact deletion using the delete-artifact action is clear and effective.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
docs/source/dev/devnotes.md (1)

477-485: Clear release instructions.
Minor: consider using “take into account” instead of “into the account”.

.github/workflows/publish_release.yaml (3)

146-187: GCS artifact copy is verbose.
Consider modularizing the repeated upload commands.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)


264-291: S3 artifact copy mirrors GCP.
Consider refactoring repeated commands.


179-182: Remove trailing spaces.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between cf98367 and 7edd47c.

📒 Files selected for processing (2)
  • .github/workflows/publish_release.yaml (1 hunks)
  • docs/source/dev/devnotes.md (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/publish_release.yaml

[error] 179-179: trailing spaces

(trailing-spaces)


[error] 182-182: trailing spaces

(trailing-spaces)

🪛 LanguageTool
docs/source/dev/devnotes.md

[uncategorized] ~486-~486: A comma might be missing here.
Context: ...uckets if the tests pass * If the tests fail it will convert the release to a draft....

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🔇 Additional comments (22)
.github/workflows/publish_release.yaml (22)

1-7: Workflow header OK.


9-25: CI status job is solid.


45-56: Commit check valid.
Ensure file content matches SHA exactly.


58-66: Draft conversion step neat.


73-77: Repo checkout OK.


78-82: Python setup fine.


83-96: Thrift install uses 0.21.0 as tested.


97-109: Wheel build step correct.
Keen use of VERSION without the “v”.


110-115: Wheel artifact upload is clear.


119-124: GCP promotion job header OK.


127-137: GCP credentials setup is proper.


138-140: GCloud SDK setup OK.


141-145: Wheel artifact download fine.


188-213: Release attachments look clear.


215-223: JFrog CLI configuration is solid.


225-240: Artifactory upload steps are OK.


241-248: AWS promotion job header OK.


253-258: AWS credentials set correctly.


259-263: AWS wheel artifact download is fine.


293-298: AWS jar attachment clear.


299-315: AWS JFrog CLI steps look good.


316-330: Cleanup job is adequate.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/source/dev/devnotes.md (1)

481-486: Refine Bullet List Punctuation.
The event list is helpful. Consider a comma after "fail" in the last bullet for clarity:

- * If the tests fail it will convert the release to a draft
+ * If the tests fail, it will convert the release to a draft
🧰 Tools
🪛 LanguageTool

[uncategorized] ~486-~486: A comma might be missing here.
Context: ...actory if the tests pass * If the tests fail it will convert the release to a draft ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 7edd47c and 2c5306a.

📒 Files selected for processing (1)
  • docs/source/dev/devnotes.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/source/dev/devnotes.md

[uncategorized] ~486-~486: A comma might be missing here.
Context: ...actory if the tests pass * If the tests fail it will convert the release to a draft ...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)

🔇 Additional comments (1)
docs/source/dev/devnotes.md (1)

477-479: Clear Release Command Update.
The revised instructions for using the GH CLI/UI are clear and concise.

@chewy-zlai chewy-zlai merged commit 36a32cb into main Apr 1, 2025
4 checks passed
@chewy-zlai chewy-zlai deleted the chewy-zlai/release_promotion branch April 1, 2025 01:30
kumar-zlai pushed a commit that referenced this pull request Apr 25, 2025
## Summary

This workflow is triggered when someone creates a new Release on Github.
It first checks to see if the integration tests have passed for the
current commit in main. If not it will convert the Release to a draft.
If the tests passed, it copies the candidate version of the jars and
wheel from the canary buckets and distributes them to all of the
customer cloud buckets.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [x] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced an automated release process to streamline publication
workflows and ensure consistent artifact handling.

- **Documentation**
- Updated release instructions with clearer guidance on version tagging
and release creation options via both CLI and UI, while condensing the
explanation of the release command's functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kumar-zlai pushed a commit that referenced this pull request Apr 29, 2025
## Summary

This workflow is triggered when someone creates a new Release on Github.
It first checks to see if the integration tests have passed for the
current commit in main. If not it will convert the Release to a draft.
If the tests passed, it copies the candidate version of the jars and
wheel from the canary buckets and distributes them to all of the
customer cloud buckets.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [x] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced an automated release process to streamline publication
workflows and ensure consistent artifact handling.

- **Documentation**
- Updated release instructions with clearer guidance on version tagging
and release creation options via both CLI and UI, while condensing the
explanation of the release command's functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
This was referenced May 9, 2025
chewy-zlai added a commit that referenced this pull request May 15, 2025
## Summary

This workflow is triggered when someone creates a new Release on Github.
It first checks to see if the integration tests have passed for the
current commit in main. If not it will convert the Release to a draft.
If the tests passed, it copies the candidate version of the jars and
wheel from the canary buckets and distributes them to all of the
customer cloud buckets.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [x] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced an automated release process to streamline publication
workflows and ensure consistent artifact handling.

- **Documentation**
- Updated release instructions with clearer guidance on version tagging
and release creation options via both CLI and UI, while condensing the
explanation of the release command's functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai added a commit that referenced this pull request May 15, 2025
## Summary

This workflow is triggered when someone creates a new Release on Github.
It first checks to see if the integration tests have passed for the
current commit in main. If not it will convert the Release to a draft.
If the tests passed, it copies the candidate version of the jars and
wheel from the canary buckets and distributes them to all of the
customer cloud buckets.

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [x] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced an automated release process to streamline publication
workflows and ensure consistent artifact handling.

- **Documentation**
- Updated release instructions with clearer guidance on version tagging
and release creation options via both CLI and UI, while condensing the
explanation of the release command's functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai added a commit that referenced this pull request May 16, 2025
## Summary

This workflow is triggered when someone creates a new Release on Github.
It first cheour clientss to see if the integration tests have passed for the
current commit in main. If not it will convert the Release to a draft.
If the tests passed, it copies the candidate version of the jars and
wheel from the canary buour clientsets and distributes them to all of the
customer cloud buour clientsets.

## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [x] Integration tested
- [x] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced an automated release process to streamline publication
workflows and ensure consistent artifact handling.

- **Documentation**
- Updated release instructions with clearer guidance on version tagging
and release creation options via both CLI and UI, while condensing the
explanation of the release command's functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants