We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be nice to have a release channel again as we had in 3.7
See: channels: latest/stable: 3.10.1 2023-02-18 (372) 11MB classic latest/candidate: ↑ latest/beta: ↑ latest/edge: 3.11.1 2023-02-18 (376) 12MB classic 3.7/stable: 3.7.0 2021-09-16 (353) 11MB classic 3.7/candidate: ↑ 3.7/beta: ↑ 3.7/edge: ↑ 3.6/stable: 3.6.3 2021-07-14 (350) 10MB classic 3.6/candidate: ↑ 3.6/beta: ↑ 3.6/edge: ↑ 3.5/stable: 3.5.4 2021-04-15 (336) 9MB classic
It would allow to limit snap upgrades to a certain max version.
No response
The text was updated successfully, but these errors were encountered:
@jnsgruk Is it possible with our new CI? Like dev channel in sublime?
Sorry, something went wrong.
Yeh it's definitely possible - it's just a fair bit of maintenance to open the new tracks etc.
In general the clients remain pretty backward compatible, and I'm not sure there is a an advantage to a new track for every release.
It is now possible to install particular revisions, which are tied to versions per the tags in this repo?
No branches or pull requests
What changes would you like?
It would be nice to have a release channel again as we had in 3.7
See:
channels:
latest/stable: 3.10.1 2023-02-18 (372) 11MB classic
latest/candidate: ↑
latest/beta: ↑
latest/edge: 3.11.1 2023-02-18 (376) 12MB classic
3.7/stable: 3.7.0 2021-09-16 (353) 11MB classic
3.7/candidate: ↑
3.7/beta: ↑
3.7/edge: ↑
3.6/stable: 3.6.3 2021-07-14 (350) 10MB classic
3.6/candidate: ↑
3.6/beta: ↑
3.6/edge: ↑
3.5/stable: 3.5.4 2021-04-15 (336) 9MB classic
It would allow to limit snap upgrades to a certain max version.
Any extra information?
No response
The text was updated successfully, but these errors were encountered: