Repository navigation
Switch branches on p5.js so that 2.x is the main branch #8871
Description
Activity
- added a parent issue
on Jun 3, 2026 Note after Discord question: if by the time the switch happens there is only minor bugfixes and documentation updates in a branch, a patch will be released right after the switch. If there is more substantial changes on that branch, then the normal 1 week of RC patch release process can be followed. Leading up to the branches switch, neither
dev-2.0normainare frozen.Here's some helpful guidance from GH on how to update your local clone:
The default branch has been renamed!
dev-2.0 is now named mainIf you have a local clone, you can update it by running the following commands.
git branch -m main v1 git branch -m dev-2.0 main git fetch origin git branch -u origin/main main git remote set-head origin -a
Reacted by eupthere
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Please see the parent issue for timeline and context. Please feel free to raise questions, concerns, or overlooked tasks; however, the work will be done by the maintainers, so it is not open to implementation volunteers.
When this task is done, on the
p5.jsrepository, themainbranch will include p5.js version 2 latest (currentlydev-2.0), and av1branch will contain version 1 latest (currentlymain). This task does not affect the website or the editor, please see parent issue for more info.Steps we will take:
Release patches in both branches, resolve any issues if they ariseNot strictly necessary, no substantive updates to contribtior docs were madeAfter this is completed, PRs will likely need to be rebased.