Skip to content

Conversation

@eschultink
Copy link
Member

@eschultink eschultink commented Dec 15, 2025

Fixes

  • fix gcp publish, artifact name, etc.

Features

  • script to trigger artifact build via gcp actions

Change implications

  • dependencies added/changed? no
  • something important to note in future release notes? no

Note

Adds CI workflows to publish AWS/GCP bundles and Maven packages, and refactors release tooling/scripts for RC builds, non-interactive CI runs, and artifact URI outputs.

  • CI/Workflows:
    • AWS Bundle (.github/workflows/publish-aws-bundle.yaml): OIDC auth, builds and publishes to multi-region S3; summarizes artifact URIs.
    • GCP Bundle (.github/workflows/publish-gcp-bundle.yaml): simplified to delegate to script; auto-detects RC vs tag; captures and summarizes artifact URI.
    • Maven Packages (.github/workflows/publish-mvn-artifacts.yaml): publishes to GitHub Packages; handles RC vs release versions; adds summary.
  • Release Scripts:
    • Trigger via GitHub Actions (tools/release/publish-rc-bundles-via-gh.sh): triggers and watches AWS/GCP publish workflows.
    • Main release (tools/release/publish.sh): defaults PATH_TO_REPO, improved exit handling; switches bundle publishing to GH workflows; adds guidance in summaries.
    • Maven publish (local) (tools/release/publish-mvn-artifacts.sh): warns to prefer GH workflow.
  • Publish Libraries:
    • AWS (tools/release/lib/publish-aws-bundle.sh): env-configurable; adds --rc/--non-interactive; RC artifact naming; S3 metadata (gh_ref); emits ARTIFACT_URI_*; non-interactive overwrite.
    • GCP (tools/release/lib/publish-gcp-bundle.sh): same flags/RC naming; cleans local Maven cache; CI auth handling; sets gh_ref metadata; emits ARTIFACT_URI.

Written by Cursor Bugbot for commit fe29d11. This will update automatically on new commits. Configure here.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes issues with the release tooling for publishing GCP and AWS bundles, and adds new functionality to trigger artifact builds via GitHub Actions.

Key changes:

  • Fixed GCP bundle publishing with corrected artifact naming for RC builds
  • Added GitHub Actions workflows for automated AWS/GCP bundle publishing with OIDC authentication
  • Created new script to trigger RC bundle builds via GitHub CLI

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
tools/release/publish.sh Updated error handling to capture exit codes and properly exit on failures
tools/release/publish-rc-bundles-via-gh.sh New script to trigger and monitor AWS/GCP bundle publishing workflows via GitHub Actions
tools/release/publish-gcp-bundle.sh Added RC build support, improved CI authentication detection, and added metadata tracking
tools/release/publish-aws-bundle.sh Made configuration environment-variable based and added metadata tracking for GitHub refs
java/pom.xml Version bump from 0.5.14 to 0.5.15
.github/workflows/publish-gcp-bundle.yaml Simplified workflow to delegate to publish-gcp-bundle.sh script
.github/workflows/publish-aws-bundle.yaml New workflow for publishing AWS bundles with OIDC authentication
Comments suppressed due to low confidence (1)

tools/release/publish-gcp-bundle.sh:1

  • Missing -r flag for jq to output raw string. The command should be --jq '.conclusion // "unknown"' with the -r flag included in the jq invocation itself, not as a separate option to gh.
#!/bin/bash

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@eschultink eschultink enabled auto-merge (squash) December 15, 2025 23:38
Base automatically changed from rc-v0.5.15 to main December 16, 2025 19:22
@eschultink eschultink changed the base branch from main to rc-v0.5.16 December 16, 2025 22:56
exit 1
fi

printf "${YELLOW}WARNING: this is not recommended; use ${BLUE}gh run publish-mvn-artifacts.yaml --ref v0.5.15${NC}${YELLOW} instead. That will be a more reliable fresh build.${NC}\n"
Copy link

Choose a reason for hiding this comment

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

Bug: Undefined YELLOW color variable in warning message

The newly added warning message on line 20 uses ${YELLOW} but this variable is never defined in the script. Lines 3-6 define GREEN, RED, BLUE, and NC, but not YELLOW. Other scripts like publish-aws-bundle.sh and publish-gcp-bundle.sh properly define YELLOW='\033[1;33m'. The undefined variable expands to an empty string, so the warning message won't be displayed in yellow as intended.

Fix in Cursor Fix in Web


# Create ZIP filename for GCP Cloud Functions
ZIP_FILENAME="${JAR_NAME}-${VERSION}.zip"
# RC builds should have artifact name like: psoxy-gcp-0.5.15-rc.zip
Copy link
Member

Choose a reason for hiding this comment

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

why zips in GCS instead of jars?

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