Update version to 0.3 #30
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So far there hasn't been any release of dvwebloader, with the old version being reported in the UI as v0.2. I suggest that after merging recent PRs (#27, #28, #29, any response to #26 (merged but required additional changes)) that we update to v0.3.
This version should continue to be compatible with 5.13+ although it does fix an issue with fav icons (the path to get these from Dataverse changes from including javax to including jakarta when we updated to EE10/Payara 6) so that part is now compatible with 6.x rather than 5.13. (It was clearly non-fatal as dvwebloader was working with 6.x before and other than the fav icons, the new version should work with 5.x).
Whether it is also time to create a tag/release is tbd. If someone is interested in doing the work, it probably makes sense, but we could also just leave it live until we decide on a 1.0.