--- title: TYPO3 Core Development to Change Branch Name url: "https://news.typo3.com/article/typo3-core-development-to-change-branch-name" description: TYPO3 monorepo branch name changes from master to main. image: "https://news.typo3.com/_assets/d1e01514e4c4a5b3147940fa2ec50682/Images/og-image-news.jpg" date: 2026-06-11 modified: 2026-06-11 categories: - "Developer & Technology" - "Product Updates & Roadmap" --- # TYPO3 Core Development to Change Branch Name - [Developer & Technology](https://news.typo3.com/article/category/developer-technology) - [Product Updates & Roadmap](https://news.typo3.com/article/category/product-updates-roadmap) TYPO3 Core Development to Change Branch Name ============================================ 28 November 2021 ![](https://news.typo3.com/fileadmin/_processed_/5/3/csm_typo3-renamed-master-branch_fb46047dcf.webp) TYPO3 monorepo branch name changes from master to main. - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/860e9e538aa963a3600a2488dff48070.jpeg)[Benni Mack](https://news.typo3.com/article/author/benni-mack) In recent years, larger Git-based solutions (such as GitHub and GitLab) changed the primary development branch name from *master* to *main*. TYPO3 Core Development uses the [Git](https://git-scm.com/) versioning system and its review system, [Gerrit](https://www.gerritcodereview.com/). When people create their new repositories on GitHub or GitLab, their default branch is called *main*, and TYPO3 is now keeping in sync with the common standard. **TYPO3’s main development branch will be renamed on November 29, 2021 on** [**github.com/typo3/typo3**](https://github.com/typo3/typo3)  **and** [**review.typo3.org**](https://review.typo3.org/)**.** Other related tools and packages have already adapted “main” in the past months, such as TYPO3’s testing framework or the separate icon repository. Why Change? ----------- For better, more understandable and more welcoming contributions! TYPO3 values inclusivity and making all contributors feel welcome and comfortable. For new developers, it’s easier to understand that our main development branch is called *main* and not *master*—the name of which sometimes needed explaining. This change is a small but important step that TYPO3 can make to ease friction when contributing, by using a familiar naming convention. For more reasons about this change, read the related news from GitHub and GitLab: - [The default branch for newly-created repositories is now main](https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/) - [The new Git default branch name](https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/) What Does This Mean For Contributors? ------------------------------------- The only change for your existing setup is to push to *refs/for/main* instead of *refs/for/master*, and to track the origin’s *main* branch instead of the *master* branch. Adapting your current development repository clone works as follows: ``` # Make sure that git pull loads from the "main" branch git branch --set-upstream-to origin/main # Rename your current "master" branch locally to "main" to match TYPO3's naming scheme git branch -m master main ``` For commit messages, all newly merged code will contain the “Releases: main” line instead of the “Releases: master” line. The Core mergers will ensure this before merging any new changes. What Does This Mean For Extension Authors? ------------------------------------------ Extension authors using the latest *dev-master* from Packagist should note that requiring *typo3/cms-core:dev-master* will no longer work. Instead of requiring the latest development branch, it is recommended you require the version that this branch represents, which currently is *^12.0@dev*. Due to branch aliases being set, you’ll always get the current main development branch, no matter how it is named. If this does not cover your intention, you need to require *typo3/cms-core:dev-main* now. Need To Know More? ------------------ You can chat with the Core Team about this change in the comments section below. ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/d2f68d86720b93361f6910922465f559.jpeg) About the Author [Benni Mack](https://news.typo3.com/article/author/benni-mack) CTO at b13,Stuttgart, Germany [Website](https://b13.com/)[Twitter](https://twitter.com/bennimack)[LinkedIn](https://www.linkedin.com/in/benjaminmack/) Being the CTO at b13 GmbH, Benni is the TYPO3 Core Project Lead and one of the driving forces behind the TYPO3 community in the last years. [More posts by this author](https://news.typo3.com/article/author/benni-mack) Additional contributors ----------------------- - Proofreader - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/49aa12815610e985a3a94122712538f2.jpeg)Felicity Brand - Publisher - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/d2606120ccc43c7846fe40337be2bc1e.png)Mathias Bolt Lesniak