Roku’s developer repositories have moved from GitHub to GitLab. This is an already-completed migration: the developer-documentation repository was archived on GitHub on October 15, 2026, and Roku’s official forum confirmed the move on October 16. If your build still uses the old locations, update the dependencies you actually use before experimenting with the RSG 2.0 SDK beta scheduled for October 29. The repository move and beta availability are separate milestones. [1][2][3]
Inventory every repository reference
Roku’s announcement covers developer documentation, sample apps and tooling. It tells developers to update stored URLs, local clones, submodules, pipelines, release-artifact fetches, Git-based package dependencies and raw-file links. Knowledge bases and coding-assistant indexes need new source URLs and a fresh crawl too. [1]
For your team, a useful inventory has three fields: the old address, what consumes it and how you will verify the replacement. A bookmark has a different failure mode from a dependency that a clean CI runner must download. Treat each place as a separate item rather than assuming one successful browser visit proves the migration is finished.
Check which remote you are about to change
Git’s remote commands let you inspect configured repositories and change their URLs. Start with git remote -v. Check the relevant address with git remote get-url followed by the remote’s name. If origin points to your own fork, do not replace it merely because an upstream project moved. A separate upstream remote may be the one that needs updating. [4]
For a clone whose origin really is Roku’s developer-documentation repository, a concrete URL-change example is: git remote set-url origin https://gitlab.com/rokudev/dev-doc.git. Confirm the configured URL afterward. This example changes the remote address; it does not by itself prove that your application builds or that your selected revision is available. [2][4]
Submodule configuration needs its own check
A submodule URL can be recorded in .gitmodules while an initialized local checkout also has URL configuration in .git/config. Git documents git submodule sync as the way to synchronize initialized submodules’ remote URL settings with .gitmodules. The --recursive option also traverses registered nested submodules. [5]
After reviewing the intended .gitmodules changes, synchronize the relevant submodules and test the checkout path your build uses. Keep a record of the expected revision. Updating an address and deliberately upgrading a dependency answer different questions; combining them makes a later failure harder to diagnose.
Verify the path a fresh build will take
- Check pipeline scripts, package manifests and any stored raw-file or release-download addresses that reference Roku’s old repositories. [1]
- Run the project’s normal checkout and build procedure in a disposable clean workspace. Record whether fetching the intended dependency and building the app both succeed.
- Review any access or authentication failure separately from a missing revision or a changed build requirement. Fixing a URL does not automatically resolve all three.
- Refresh internal setup notes after verification, so the next developer starts from the tested configuration.
Separate beta access from app publishing
Roku’s RSG 2.0 FAQ schedules public SDK, documentation and sample availability on GitLab for October 29, 2026. It says BrightScript remains supported and can coexist with TypeScript. The move therefore does not establish a requirement to rewrite every existing channel. [3]
The FAQ also distinguishes development access from distribution: ordinary self-service publishing follows general availability. Publishing an SDK-built app during beta requires explicit approval and hands-on support from Roku. Plan an evaluation milestone for the beta rather than treating the date as an automatic production launch. [3]
The useful outcome is a verified set of repository references and a separate SDK evaluation plan. No Roku app, CI pipeline or device was migrated or tested for this article; the verification steps above are a recommended workflow, not a report of completed application testing.
Check your migration plan
Sources
- [1] Roku developer migration announcement, October 16, 2026: https://forum.developer.roku.com/t/roku-developer-repositories-have-moved-to-gitlab/11655
- [2] Archived official developer-documentation repository: https://github.com/rokudev/dev-doc
- [3] Roku RSG 2.0 FAQ, current published schedule and publishing limits: https://forum.developer.roku.com/t/rsg-2-0-faqs/11453
- [5] Git submodule reference: https://git-scm.com/docs/git-submodule
