Migrate to roku-deploy v4 and Roku Cloud Emulator support- #399 - #398
Merged
Conversation
Move every roku-deploy call to the v4 named-options API and the unified device option: - publish -> sideload (explicit close: false and deleteDevChannel: false to preserve existing behavior) - pressHomeButton -> keyPress with the home key - deleteInstalledChannel -> deleteDevChannel - prepublishToStaging -> stage, zipFolder -> zip - getFilePaths named options (dest is staging-relative; ProjectManager absolutizes) - getOptions/getOutputZipFilePath replaced with RokuDeploy.defaults and the getStagingDir/getOutputZipPath resolvers - host/remotePort call sites now build a device option; the private BrightScriptDebugSession.device getter is the single place the launch configuration becomes a roku-deploy device config
TwitchBronBron
approved these changes
Aug 3, 2026
# Conflicts: # src/debugSession/BrightScriptDebugSession.ts
chrisdp
force-pushed
the
feature/roku-deploy-v4
branch
from
August 5, 2026 16:49
cb04ee2 to
1b1e3ac
Compare
TwitchBronBron
marked this pull request as ready for review
August 7, 2026 17:39
Co-authored-by: Bronley Plumb <bronley@gmail.com>
chrisdp
changed the title
chrisdp
enabled auto-merge (squash)
August 7, 2026 18:42
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
3 participants
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.
Moves every roku-deploy call to the v4 named-options API and the unified
deviceoption (roku-deploy PR rokucommunity/roku-deploy#323, plus the defaults/resolvers from rokucommunity/roku-deploy#330).publish->sideload, passing explicitclose: falseanddeleteDevChannel: falsesince v4 enables both by default and roku-debug handles them itselfpressHomeButton->keyPresswith the home keydeleteInstalledChannel->deleteDevChannelprepublishToStaging->stage,zipFolder->zip,getFilePathsnamed options (dest paths are now staging-relative, so ProjectManager absolutizes them)getOptions/getOutputZipFilePathare gone in v4; replaced withRokuDeploy.defaultsand thegetStagingDir/getOutputZipPathresolvershost/remotePortcall site now builds adeviceoption; the privateBrightScriptDebugSession.devicegetter is the single place the launch configuration becomes a roku-deploy device config, so future addressing schemes (like the Roku Cloud Emulator) only need to be handled thereDraft: builds against a local roku-deploy checkout of the unified-device-option work; the package.json bump will follow separately once a v4 alpha containing it is published.