Branch Reorganization Update – 2 September 2025

Open
#624 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
release

Research direction

No source files, tests, or entry points are named. Review the repository branch settings and the 6.1.x release lineage first; this is complete when main is the default development branch, master_old remains available, and the documented branch arrangement matches the repository.

Written by the indexing model from the issue text.

Description

Branch Reorganization Update – 2 September 2025

What This Means

The default branch formerly called master will be renamed master_old.
A new default branch, main, will be created from the latest stable release branch 6.1.x.

You may continue to use master_old, but all new changes will be developed on the main branch.
Please note that the main branch may not include certain changes previously made in master_old.

Why We Are Doing This

The development history in master had diverged from the stable release cycle, which made releases and maintenance less predictable. To keep things clearer and more consistent, we’re aligning future development with the latest stable release of @formio/react. This reorganization will help ensure a more reliable foundation for new features and contributions.

Questions or Feedback

Enterprise users: If you are an Enterprise Form.io customer, these changes should not impact your deployments. For additional information, please contact your customer support representative.
Open-source community: If you have questions, run into issues, or want to share feedback on this change, please join the conversation in this issue.

We value your input and appreciate your contributions as we move forward with a cleaner branch strategy.

Dominant language
TypeScript
Stars
371
Forks
309
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from formio/react

All issues in formio/react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.