Can we still maintain a 2.x branch?
See original GitHub issue2 → 3 introduced breaking changes and some people may still have to stuck with 2.x for some time. Can we still maintain a 2.x
branch and release more 2.x versions to fix security vulnerabilities inside dependencies (by just updating package.json
)? eg. 2.7.3
had fixed the version of request
to 2.81.0
which depend on a risky hoek@4.2.1
. We may just need to update request
to 2.82.0
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
git working on two branches simultaneously - Stack Overflow
If you want to commit/pull to the same repository with two different working copies, you could create a bare repository and clone it...
Read more >Branches in a Nutshell - Git SCM
Branching means you diverge from the main line of development and continue to do work without messing with that main line. In many...
Read more >About protected branches - GitHub Docs
You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and...
Read more >Should the "master" branch be the last stable one?
Hi, Today I just realized that pkp's master's branch is not running the last stable ojs version… Is there a good reason for...
Read more >More ways to keep your pull request branch up-to-date
When your pull request's branch is out of date with the base branch, you now have the option to update it by rebasing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s actually not so. There are tons of projects depending on
less
itself. A fork doesn’t automatically change those references. I don’t want to keep telling those 2.x users “hey switch to my fork because Less is not maintaining 2.x anymore”. This involves a lot, there are very deep dependency chain there in modern JavaScript projects. A full “open-source minded” is not equal to ignoring the reality.Closing as won’t fix.