chore: bump version

[sleepdefic1t]

Proposed changes

This PR bumps version to 1.2.0 and will match incoming 1.2.0-arduino tag.
see #79 for more info.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe:

Checklist

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[ghost]

@air1one @faustbrian - please review this in the next few days. Be sure to explicitly select labels so I know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

[codecov-io]

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #80   +/-   ##
======================================
  Coverage    96.4%   96.4%           
======================================
  Files          14      14           
  Lines         250     250           
======================================
  Hits          241     241           
  Misses          9       9

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a8c1e2...9fddb98. Read the comment docs.

[ghost]

@sleepdefic1t The ci/circleci: build-linux-gcc7 job is failing as of 13aed2edd274d38a7f08b6fd8720cc49f416d42b. Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

[faustbrian]

Are we really required to do duplicate tags for the same code? Shouldn't everything work with a single tag now that the arduino config is setup?

[sleepdefic1t]

Yes, and no.

Arduino branch will have a different folder structure compatible with Arduino’s library manager.

The Arduino tags should target the Arduino branch; regular tag should target master.

what’s basically going on:
master | 1.2.0
master >> Arduino Script >> arduino branch | 1.2.0-arduino

Using two releases is per @kristjank and discussion here:
https://forum.arduino.cc/index.php?topic=596617.0

The Library Manager indexer job just works off of Git tags. As long as the tag points to something that is compliant, it's fine. You could have one branch of the repo with the Library Manager compatible structure that you point the Library Manager tags at, and another branch of the repository with your existing structure. You should also be able to create tags that point to the non-compliant branch and the Library Manager indexer should just ignore those.

The alternative would be a completely separate Arduino repo with nearly identical code, just laid out differently than PlatformIO and Desktop builds.

I’m open to more discussion if you feel it’s warranted though.

[faustbrian]

Makes sense now, thanks for the link.