fix(ci): eliminate redundant CI runs and migrate release-please#70
Merged
fix(ci): eliminate redundant CI runs and migrate release-please#70
Conversation
…ushes - Skip test, lint, and Docker build jobs on release-please PRs (metadata-only changes) - Remove duplicate test-unit/test-integration steps on main (test-coverage already runs full suite) - Migrate from deprecated google-github-actions/release-please-action to googleapis/release-please-action - Update docker-validation to accept skipped upstream jobs gracefully
Contributor
There was a problem hiding this comment.
Pull request overview
This PR optimizes the CI/CD workflow by eliminating redundant test runs and migrating to the current release-please action. The changes reduce CI execution time by approximately 15 minutes per merge to main by skipping unnecessary validation on release-please PRs and removing duplicate test steps.
Changes:
- Add skip conditions to all CI jobs (test, lint, docker builds) for release-please PRs that only modify CHANGELOG.md and version files
- Remove duplicate
test-unitandtest-integrationsteps on main branch (already covered bytest-coverage) - Migrate from deprecated
google-github-actions/release-please-action@v4togoogleapis/release-please-action@v4 - Update
docker-validationgate to accept bothsuccessandskippedjob results
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Added skip conditions to test, lint, and docker jobs; removed duplicate test steps; migrated release-please action; updated validation gate logic |
uv.lock |
Version bump from 1.0.1 to 1.1.0 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jhcipar
approved these changes
Feb 26, 2026
deanq
added a commit
that referenced
this pull request
Feb 26, 2026
* fix(ci): eliminate redundant CI runs on release-please PRs and main pushes - Skip test, lint, and Docker build jobs on release-please PRs (metadata-only changes) - Remove duplicate test-unit/test-integration steps on main (test-coverage already runs full suite) - Migrate from deprecated google-github-actions/release-please-action to googleapis/release-please-action - Update docker-validation to accept skipped upstream jobs gracefully * chore: sync uv.lock version to 1.1.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CHANGELOG.mdandpyproject.tomlversion, which were already validated on the push-to-main runtest-unitandtest-integrationsteps on main branch —test-coveragealready runs the full suite, so these doubled test time per Python versiongoogle-github-actions/release-please-action@v4togoogleapis/release-please-action@v4docker-validationgate to acceptskippedupstream jobs gracefullySaves ~15 min of CI time per merge to main.
Test plan
docker-validationpasses when upstream jobs are skipped (release-please PR scenario)googleapis/namespace