Finalize Toolkit for Release #825
Merged
Conversation
This file contains hidden or 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.
This updates version numbers in all the example projects, the package.swift file, and the README. The system requirements in the README is now just a link to the SDK requirements, as they are the same.
This will need to wait to be merged until the Swift SDK is live. After this gets merged, the
v.next -> mainPR (#828) can be merged and the Github Release published (after final testing).Regarding the latest system requirements: instead of updating these every release, I'd like to just reference the SDK requirements on the Esri Dev site; that way there will be no incompatibility between the two.