Skip to content

Release v0.3.0#660

Open
github-actions[bot] wants to merge 15 commits into
mainfrom
release/v0.3.0
Open

Release v0.3.0#660
github-actions[bot] wants to merge 15 commits into
mainfrom
release/v0.3.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 1, 2026

Release v0.3.0

This updates and releases GiGL version from 0.2.0 to 0.3.0.

Info:

What's Next:

Please create a new release from the tag.

This PR was automatically created by the Create Release workflow.

Comment thread scripts/bump_version.py
Copy link
Copy Markdown
Collaborator

@kmontemayor2-sc kmontemayor2-sc left a comment

Choose a reason for hiding this comment

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

shall we also update CHANGELOG?

Comment thread scripts/bump_version.py
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread gigl-core/pyproject.toml
@mkolodner-sc mkolodner-sc enabled auto-merge June 2, 2026 16:20
@mkolodner-sc mkolodner-sc added this pull request to the merge queue Jun 2, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 2, 2026
@mkolodner-sc mkolodner-sc added this pull request to the merge queue Jun 2, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 2, 2026
@mkolodner-sc mkolodner-sc added this pull request to the merge queue Jun 2, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 2, 2026
@mkolodner-sc mkolodner-sc added this pull request to the merge queue Jun 2, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jun 2, 2026
kmonte and others added 2 commits June 2, 2026 23:38
…orkers

get_graph_store_info() reads get_resource_config() to build the readiness
URI (added in #533), but the launched Vertex AI workers had no
GIGL_RESOURCE_CONFIG_URI in their env, so they failed with "No resource
config provided". Inject it via the compute pool's environment_variables,
which launch_graph_store_job propagates to both compute and storage pools.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…test workers

The test runner's resource config URI may be a local path that does not
exist on the worker Docker image, so passing it directly to the workers via
GIGL_RESOURCE_CONFIG_URI would not be readable. Instead, upload the
in-memory resource config to the regional bucket (accessible to workers over
GCS), pass that URI to the workers, and delete it in tearDown.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mkolodner-sc
Copy link
Copy Markdown
Collaborator

/integration_test

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Jun 3, 2026

GiGL Automation

@ 16:25:19UTC : 🔄 Integration Test started.

@ 17:40:41UTC : ✅ Workflow completed successfully.

@mkolodner-sc
Copy link
Copy Markdown
Collaborator

/help

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Jun 3, 2026

GiGL Automation

@ 16:27:25UTC :

🤖 Available PR Commands

You can trigger the following workflows by commenting on this PR:

  • /help - Checkout code
  • /unit_test_py - Run Python Unit Tests
  • /unit_test_cpp - Run C++ Unit Tests
  • /unit_test_scala - Run Scala Unit Tests
  • /integration_test - Run Integration Tests
  • /e2e_test - Run E2E Tests
  • /notebook_tests - Run Example Notebooks Tests
  • /lint_test - Run Linting Tests

💡 Usage: Simply comment on this PR with any of the commands above (e.g., /unit_test)

⏱️ Note: Commands may take some time to complete. Progress updates will be posted as comments.

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Jun 3, 2026

GiGL Automation

@ 16:34:00UTC : Starting to build base images for CUDA and CPU.
This may take a while, please be patient.
The images will be pushed to the GCP Artifact Registry.
Once done, the workflow will update the gigl/dep_vars.env file with the new image names.

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Jun 3, 2026

GiGL Automation

@ 16:44:21UTC : Built and pushed new images:

  • CUDA base image: us-central1-docker.pkg.dev/external-snap-ci-github-gigl/public-gigl/gigl-cuda-base:6db83bdc98b2da65ac80243ce08cd8b37b3ee85f.110.1
  • CPU base image: us-central1-docker.pkg.dev/external-snap-ci-github-gigl/public-gigl/gigl-cpu-base:6db83bdc98b2da65ac80243ce08cd8b37b3ee85f.110.1
  • Dataflow base image: us-central1-docker.pkg.dev/external-snap-ci-github-gigl/public-gigl/gigl-dataflow-base:6db83bdc98b2da65ac80243ce08cd8b37b3ee85f.110.1
  • Builder image: us-central1-docker.pkg.dev/external-snap-ci-github-gigl/gigl-base-images/gigl-builder:6db83bdc98b2da65ac80243ce08cd8b37b3ee85f.110.1

Updated gigl/dep_vars.env with new image names.
Updated .github/cloud_builder/run_command_on_pr_cloud_build.yaml with new builder image.

@mkolodner-sc
Copy link
Copy Markdown
Collaborator

/integration_test

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Jun 3, 2026

GiGL Automation

@ 16:52:57UTC : 🔄 Integration Test started.

@ 18:07:09UTC : ✅ Workflow completed successfully.

Copy link
Copy Markdown
Collaborator

@svij-sc svij-sc left a comment

Choose a reason for hiding this comment

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

Lets have a clean change log prior to merging.
I see we are doing networking_test because something was failing.

Ideally these should be in main.

@kmontemayor2-sc
Copy link
Copy Markdown
Collaborator

@svij-sc me and @mkolodner-sc are testing the change, long story short there's some bugs in our tests were just re-surfaced with this release, I have #666 as a separate PR if this works. And I'm working on a different change (PR coming soon) for a more wholistic fix that doesn't rely on the base images for the tests

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