Skip to content
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

use correct version in SQL upgrade script #6293 #6294

Merged
merged 1 commit into from
Oct 21, 2019

Conversation

pdurbin
Copy link
Member

@pdurbin pdurbin commented Oct 18, 2019

closes #6293

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)."
@coveralls
Copy link

Coverage Status

Coverage remained the same at 19.461% when pulling 48ebf29 on 6293-sql-script-rename into 4539927 on develop.

@djbrooke djbrooke self-assigned this Oct 21, 2019
@djbrooke djbrooke removed their assignment Oct 21, 2019
@kcondon kcondon self-assigned this Oct 21, 2019
@kcondon kcondon merged commit 93270b0 into develop Oct 21, 2019
@kcondon kcondon deleted the 6293-sql-script-rename branch October 21, 2019 17:52
@pdurbin pdurbin mentioned this pull request Oct 21, 2019
5 tasks
@djbrooke djbrooke added this to the 4.18 milestone Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rename V4.18.0.1__5991-update-scribejava.sql
4 participants