+fastlane.tools

[mxcl]

Closes #363

[what-the-diff]

• The fastlane.tools directory was created
• A package file and a shell script were added to the new directory
• The build, test, provides and dependencies sections of the package file are defined

[joshdholtz]

@mxcl Hey! 👋 fastlane lead maintainer here... Thank you so much for adding fastlane ❤️

I'm just learning about tea but is there anything I need to do with fastlane when new versions are made for tea to seem them? It seems like it just looks at the latest tag on GitHub?

[jhheider]

@joshdholtz publish a GitHub release with a version tag (deeply preferably semver ;) ) and our existing automation should catch and trigger the new build within 5 minutes. We follow up on builds that fail (and they make issues in the pantry.core repository), and we're pretty good about filing bug reports and opening PRs if we detect something upstream might want to know.

We're happy you're happy! Hopefully, tea makes it easier for people to start using fastlane.

[mxcl]

Hey @joshdholtz thanks for your attention!

As Jacob said we build automatically on GitHub releases. tea is heavily developer focused so we try to make all versions available to our users ASAP then it's up to the user if they update or remain pinned to a previous version.

Stay tuned! We got some really exciting things planned this year!