Repository navigation
chore(release): 0.2.3 - #13
Merged
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.
Release 0.2.3
pubspec.yamlandSdkInfo.version→0.2.3(the version sent assdkVersionand inX-LinkForty-SDK).CHANGELOG.md: 0.2.3 entry.README.md: the install snippet now readslinkforty_flutter: ^0.2.3. For a 0.x package,^0.1.0allows only>=0.1.0 <0.2.0, so it installed 0.1.1.Fixed
Z, and empty attribution fields are left out instead of sent asnull. Events already queued on a device are sent in the corrected form when the queue flushes (fix(models): enforce UTC ISO 8601 timestamps and omit null attribution fields in EventRequest #11, fixes Event tracking fails with 400 VALIDATION_ERROR on organic app opens #10). Thanks @arman-uc.flutter test: 129 passed.flutter pub publish --dry-run: 0 warnings.After merge
Then create the GitHub release for
v0.2.3from the CHANGELOG section and close #10.