Multi-Version SDK Publishing: Path Detection and Serial Execution Fixes #76
Conversation
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.
This PR fixes critical issues in the SDK publishing workflow and updates documentation:
Path Detection: Replaced unreliable
contains(github.event.head_commit.modified, ...)withdorny/paths-filter@v2for reliable detection of which API versions were modified.Serial Publishing: Fixed gate job to properly enforce serial execution—v20250224 now correctly waits for v20111101 to complete before publishing.
Gate Job Pattern: The gate job (
gate-v20111101-complete) depends onrelease-v20111101via theneedsarray, but usesif: always()to override the default skip behavior. This critical detail allows the gate to run even when v20111101 is skipped (not modified), unblocking v20250224 while maintaining serial ordering when both versions change.v3.0.0 Changelog: Improved v3.0.0 entry with proper breaking change documentation and migration guide links.
Documentation: Updated workflow and adding-new-version docs to reflect current detect-changes pattern and gate job implementation.