Repository navigation
Use repository dispatch for Bedrock version updates - #473
Merged
Merged
Conversation
extremeheat
added a commit
that referenced
this pull request
Oct 29, 2026
* Update * Release 3.119.0 * Trigger Bedrock updates with repository dispatch (#473) --------- Co-authored-by: rom1504bot <rom1504bot@users.noreply.github.com> Co-authored-by: extremeheat <extreme@protonmail.ch>
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.
The release workflow published minecraft-data successfully but its workflow_dispatch request to bedrock-protocol failed with HTTP 403. Send a repository_dispatch event of type minecraft-data-release instead, which the existing Bedrock handler already accepts.
Include the published npm version as client_payload.minecraftDataVersion so the handler installs the exact release. Keep the existing condition that sends notifications only after publication.
Validation: parsed workflow YAML, executed the jq payload builder with version 3.118.0, and checked the event type and payload key against the receiving workflow. No live dispatch was sent. PAT_PASSWORD still needs Contents write access to PrismarineJS/bedrock-protocol; this change does not establish that permission.