-
Notifications
You must be signed in to change notification settings - Fork 492
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
rename V4.18.0.1__5991-update-scribejava.sql #6293
Comments
pdurbin
added a commit
that referenced
this issue
Oct 18, 2019
Correct being defined at http://guides.dataverse.org/en/4.17/developers/sql-upgrade-scripts.html#how-to-create-a-sql-upgrade-script "Use a version like "4.11.0.1" in the example above where the previously released version was 4.11, ensuring that the version number is unique. Note that this is not the version that you expect the code changes to be included in (4.12 in this example)."
I just created pull request #6294 to fix this. |
Ui, nice catch! Sorry for mixing up the numbers, I had in mind that we use next release. Thanks again! |
kcondon
added a commit
that referenced
this issue
Oct 21, 2019
use correct version in SQL upgrade script #6293
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whoops, src/main/resources/db/migration/V4.18.0.1__5991-update-scribejava.sql should have 4.17 instead of 4.18 in it. Good catch, @landreev
The text was updated successfully, but these errors were encountered: