We only support 2 major versions for security patches
| Version | Branch | Supported | Specific Tags |
|---|---|---|---|
| 4.x | v4.x | ✅ | v4 |
| 3.x | v3.x | ✅ | |
| < 2.x | ❌ | v2.x, v1.1.x |
A GitHub repository can used one of the available branches as action inside its workflows.
When a branch is not supported anymore, the following process occurs
- Since
v4.xbranch, the branch will be deleted 2 major versions after- So
v4.xbranch will be deleted whenv7.xbranch will have its first release - prefer the
v4tag tov4.xbranch as reference in our workflow,
- So
- Before
v4.xbranch, the branch will be converted into a tag when the support is dropped- So
v3.xbranch will be converted as tag whenv5.xbranch will have its first release
- So
You can report a Vulnerability by my email.
Vulnerability stages :
- Reported,
- Confirmed (or declined),
- Fixed on maintained version series.
After a vulnerability fix, an GitHub issue will be created as document this vulnerability.