Enforce milestone validation before creating PlatformIO dependency PRs#390
Merged
JanPetterMG merged 1 commit intomainfrom Feb 27, 2026
Merged
Enforce milestone validation before creating PlatformIO dependency PRs#390JanPetterMG merged 1 commit intomainfrom
JanPetterMG merged 1 commit intomainfrom
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 introduces a fail-fast milestone validation step in the dependency update workflows.
Before invoking
peter-evans/create-pull-request, the workflow now verifies that:If the milestone is missing or closed, the workflow fails immediately.
Rationale
Previously, PR creation could fail during the pull request creation step when:
This could lead to repeated failed runs and PR stacking behavior.
By validating the milestone explicitly and early, the workflow:
This change improves workflow robustness, especially in fork scenarios where milestone numbers differ or are absent.