You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In ci.yml, the final sasview release name is hard-coded as sasviewX where X is the major release number. This was noted in #2700 and will be an issue when we eventually move from v6 to v7 (and beyond).
Describe the solution you'd like
The version number can be captured programmatically, so we should generate the name in .github/workflows/matrix.py so it is available for the workflows. This will also give us more flexibility in the release naming scheme.
Describe alternatives you've considered
Any automated way to handle this would be better than combing through the CI to increment a number every time we have a major release.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In ci.yml, the final sasview release name is hard-coded as
sasviewX
where X is the major release number. This was noted in #2700 and will be an issue when we eventually move from v6 to v7 (and beyond).Describe the solution you'd like
The version number can be captured programmatically, so we should generate the name in .github/workflows/matrix.py so it is available for the workflows. This will also give us more flexibility in the release naming scheme.
Describe alternatives you've considered
Any automated way to handle this would be better than combing through the CI to increment a number every time we have a major release.
The text was updated successfully, but these errors were encountered: