docs: add protocol development workflow guide#2149
Open
kuruk-mm wants to merge 2 commits into
Open
Conversation
Contributor
📦 Build Report🤖 Android
Build Status: ✅ Success 🍏 iOS
🔗 Workflow Run: View logs 🔄 Updated: 2026-05-20 17:13:27 UTC |
Document the end-to-end process for shipping protocol changes across protocol, js-sdk-toolchain, and godot-explorer, including the role of protocol-squad as an iteration channel and the cherry-pick path to main.
kuruk-mm
force-pushed
the
docs/protocol-dev-workflow
branch
from
30d194a to
c7c1567
Compare
Flow A is now "Straight to main" (default) and Flow B is "Through protocol-squad" (legacy). Reorders the sections, swaps the recommendation table and quick-reference, and updates cross-references so the protocol-squad detour is positioned as a fallback for changes whose shape is still in flux.
4 tasks
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
1 participant
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
docs/PROTOCOL_DEV_WORKFLOW.mddescribing how to land a protocol change acrossprotocol,js-sdk-toolchainandgodot-explorer.protocol-squadvsmain, the per-PR tarball flow, and the backward compatibility contract that keeps deployed scenes safe.@dcl/protocoltag to depend on while iterating vs after a feature lands.Test plan