countnazgul
commented
1 year ago Is this enough?
- branch for each version
- the main branch will always be the latest version
- the default package install (aka @latest) will point to the latest version only
- each branch will be updated with the supported changes
How long to keep updating old versions? It seems that end of support for QS is 2 years. Based on this community post
Does npm tags is the answer of how to release multiple versions of the same package?
How to implement QS version specific releases?
The Repo API is changing form version to version. Not massively but still some old methods might be changed and new methods are introduced.
Because of this latest version of this package might not behave nicely with older (not latest) QS versions.
This issue is to track the idea of how to have QS version specific releases/package