Gap between kernel version and release version #4471
chenxudong2020
started this conversation in
General
Replies: 2 comments 1 reply
-
Some people may ask what the significance of this question is, mainly to facilitate the integration of xray plug-ins such as |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
go list -m -versions github.com/xtls/xray-core
github.com/xtls/xray-core v1.0.0 v1.1.0 v1.1.1 v1.1.2 v1.1.3 v1.1.4 v1.1.5 v1.2.0 v1.2.1 v1.2.2 v1.2.3 v1.2.4 v1.3.0 v1.3.1 v1.4.0 v1.4.1 v1.4.2 v1.4.3 v1.4.4 v1.4.5 v1.5.0 v1.5.1 v1.5.2 v1.5.3 v1.5.4 v1.5.5 v1.5.6 v1.5.7 v1.5.8 v1.5.9 v1.5.10 v1.6.0 v1.6.1 v1.6.2 v1.6.3 v1.6.4 v1.6.5 v1.6.6-2 v1.6.6 v1.7.0 v1.7.1 v1.7.2 v1.7.3 v1.7.5 v1.8.0 v1.8.1 v1.8.2 v1.8.3 v1.8.4 v1.8.5 v1.8.6 v1.8.7 v1.8.8 v1.8.9 v1.8.10 v1.8.11 v1.8.12 v1.8.13 v1.8.15 v1.8.16 v1.8.17 v1.8.18 v1.8.19 v1.8.20 v1.8.21 v1.8.22 v1.8.23 v1.8.24
But the releases are already version 25. Is it possible to unify or set certain rules? It’s currently confusing.
Beta Was this translation helpful? Give feedback.
All reactions