[arduino] docs: update changelog and merge #93 from master#114
Merged
faustbrian merged 5 commits intoArkEcosystemArchive:arduinofrom Jul 16, 2019
sleepdefic1t:chore/update-changelog-and-merge-#93-from-master-arduino
Merged
[arduino] docs: update changelog and merge #93 from master#114faustbrian merged 5 commits intoArkEcosystemArchive:arduinofrom sleepdefic1t:chore/update-changelog-and-merge-#93-from-master-arduino
faustbrian merged 5 commits intoArkEcosystemArchive:arduinofrom
sleepdefic1t:chore/update-changelog-and-merge-#93-from-master-arduino
Conversation
Contributor
|
The date also needs to be updated, still says |
faustbrian
reviewed
Jul 16, 2019
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
2 participants
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 PR updates the changelog and merges
master#93 toarduino.No idea how 93 slipped through 🤷♂
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
developbranch, not themasterbranch