-
Notifications
You must be signed in to change notification settings - Fork 2
Choose exact release (such as 2.5.1) #15
New issue
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
Labels
feature
A new functionality
Comments
57 tasks
3 tasks
Totktonada
added a commit
that referenced
this issue
Feb 11, 2022
Sometimes we want to test a module against specific tarantool version, not a latest in the series. For example, 2.6 series may have 2.6.1, 2.6.2 and 2.6.3 releases and we want to setup 2.6.1. TBD: Add a test. Fixes #15
Totktonada
added a commit
that referenced
this issue
Jun 22, 2022
Sometimes we want to test a module against specific tarantool version, not a latest in the series. For example, 2.6 series may have 2.6.1, 2.6.2 and 2.6.3 releases and we want to setup 2.6.1. Fixes #15
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
Sometimes we want to test a module against specific tarantool version, not a latest in the series. For example, 2.6 series may have 2.6.1, 2.6.2 and 2.6.3 releases and we want to setup 2.6.1. Fixes #15
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
Sometimes we want to test a module against specific tarantool version, not a latest in the series. For example, 2.6 series may have 2.6.1, 2.6.2 and 2.6.3 releases and we want to setup 2.6.1. Fixes #15
Totktonada
added a commit
that referenced
this issue
Jun 23, 2022
Sometimes we want to test a module against specific tarantool version, not a latest in the series. For example, 2.6 series may have 2.6.1, 2.6.2 and 2.6.3 releases and we want to setup 2.6.1. Fixes #15
Totktonada
added a commit
to tarantool/crud
that referenced
this issue
Jun 24, 2022
The setup-tarantool action allows to define a tarantool version in the X.Y.Z form since v1.3.0 of the action. See [1]. [1]: tarantool/setup-tarantool#15
Totktonada
added a commit
to tarantool/crud
that referenced
this issue
Jul 5, 2022
The setup-tarantool action allows to define a tarantool version in the X.Y.Z form since v1.3.0 of the action. See [1]. [1]: tarantool/setup-tarantool#15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Say, setup 2.5.1 when 2.5.2 is available.
I want to use this ability, when I know a degradation of a module on a particular release (but not the last one). When I'm going to fix the problem in the module, I want to leave a regression test in CI.
The text was updated successfully, but these errors were encountered: