Cut a 1.0.0 release

[fgrehm]

Things have been working greatly for me over the past 2 years and it is about time to squash some known bugs and lock down the current feature set in prep for a potential big revamp on the project.

This is what I have in mind right now that will make up for 1.0.0:

• Attempt to trim down the image size again
• Update to latest heroku/cedar
• Buildpacks updates
  • Remove bats (only used once in almost 2 years)
  • Remove phantomjs (used once or twice in almost 2 years)
  • Update golang and fix buildpacks/golang: Nicely handle blanky git remote #94
  • Update nodejs
  • Update php
  • Fix Drupal 8 has /vendor folder and Buildpack fails #106
  • Update python
  • Update ruby and attempt to implement buildpacks/ruby: Try to handle BUNDLED WITH from Gemfile.lock #100
  • Fix inline's Improve inline buildpack #97 / buildpacks/inline: Deal with provision exit codes properly #99
  • Deal with Extract automagic port forwarding to a plugin #85
• Cover current functionality with some sort of feature tests

If you happen to come across this issue, please LMK if you want something to be kept around or have any suggestions for this release 🍻

[devekko]

I'd like these please :>

https://docs.tsuru.io/stable/using/buildpacks.html

[fgrehm]

@devekko unfortunately that's not possible given current's devstep state and based on what I've seen so far from official heroku buildpacks. They are very focused on production web apps and I use devstep for CLI tools for example. Some of devstep's (if not most of them) are based on official Heroku buildpacks with some tweaks made by me.

This is something I'd like to improve after 1.0 is out