π’ Horilla v2 is becoming the default branch β v1 is being deprioritized #1127
Pinned
horilla-opensource
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
TL;DR
Nearly all active development has been happening on
dev/v2.0for a while now β our own README and CI already assume it. We're making that official: starting July 29, 2026,2.0becomes this repo's default branch, and1.0/master(v1) is being deprioritized. This post explains what's changing and what it means for you.Which branch is which
2.0β the new default branch. This is what a plaingit clonegives you, and what GitHub pre-selects as the base for new PRs and forks. Use it to run or deploy Horilla. It's a periodic snapshot ofdev/v2.0, not where day-to-day development happens.dev/v2.0β the active integration branch. If you want to contribute code, this is what you branch from and open PRs against β not2.0.1.0/masterβ v1. Not deleted or renamed, but deprioritized (see below).What this means for v1
v1 is being deprioritized. We are not committing to a fixed support window or a guaranteed security-patch schedule for
1.0/mastergoing forward β any further fixes will be considered case-by-case, at maintainer discretion, not on a promised timeline. No new features will be backported to v1. If you're running v1 in production, we strongly recommend planning your migration to v2 now.Why now
v2 has been where the overwhelming majority of commits, features, and fixes have landed for some time. Keeping
1.0as the default branch was actively misleading β new contributors cloning the repo the normal way were getting outdated v1 code instead of what the project already recommends everywhere else.What you need to do
If you have an existing fork:
git remote add upstream https://github.com/horilla/horilla-hr.git # if you haven't already git fetch upstream git checkout -b 2.0 upstream/2.0If you have an open pull request:
dev/v2.0already? No action needed.1.0ormaster? Let us know in this thread β happy to help retarget todev/v2.0, or discuss whether it still makes sense on v1.If you're starting fresh:
git clonegets you2.0automatically from July 29 onward.dev/v2.0explicitly:git clone -b dev/v2.0 https://github.com/horilla/horilla-hr.git. Note: when you open your PR, GitHub will default the base branch to2.0β change it todev/v2.0before submitting.Questions
Drop them in this thread β we'll keep it updated and pinned through the transition.
All reactions