Branch Reorganization Update – 2 September 2025
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from formio/react
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
onChange `modified` property remains false when file component is updatedMay be free again @ZenMasterJacob20011 claimed this 295 days ago, and no pull request is open. Open
-
FormBuilder onChange callback not triggered when options prop is providedMay be free again @Victoriya25 claimed this 337 days ago, and no pull request is open. Open
-
FormBuilder with OnChange broke textareaMay be free again @lane-formio claimed this 309 days ago, and no pull request is open. Open
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day