v1.0.0
func-e 1.0.0 adds latest patch syntax and adds Linux packages.
We chose to call this 1.0 as things work pretty well. func-e has been downloaded over 50k times since it was relaunched 3 months ago. While we know things aren't perfect and new features will arise, 1.0 means stability. We won't delete commands or make them incompatible intentionally. If you notice otherwise, please raise an issue!
Check out our issues labeled hacktoberfest. You can join other newcomers, such as @clavinjune, who helped the project though hacking.
Also, if you are interested in learning more about Envoy with func-e, check out Tetrate's new Envoy Fundamentals class.
Finally, if you are enjoying func-e please star the repo as contributors like seeing them. Now, on to the changes!
Latest patch syntax
Before, you could leave out an Envoy version or choose a one, like func-e use 1.19.1. You can now choose a minor version, like func-e use 1.19. If there's ever a new patch, it will be downloaded automatically. This is helpful for matrix testing where you want to ensure your configuration is likely work, yet run with the latest fixes.
This was a lot of work! Thanks @clavinjune, @codefromthecrypt, @dio and @mathetake for developing various aspects of this.
Linux packages
Before, you could only install func-e on Linux using curl or homebrew. We added RPM and Debian packages which you can download below and use on CentOS or Ubuntu. Thanks to @codefromthecrypt for leading this, @dio for helping with the integration tests and @mathetake for review.
Infrastructure
Notably, our end-to-end tests run on more realistic images, and edge cases like kill -9 are now tested. Our build is more coherent, moving a lot of logic from workflows and 3rd party tools into native Makefile. This makes it easier to test distributions without publishing them, and also makes GOROOT selection more portable. Re-runs are faster as most targets use file prerequisites to eliminate redundant runs. Even the skeleton release notes are now generated. Thanks a lot to @codefromthecrypt, @dio and @mathetake for the hard work here. Better infrastructure means smoother and more reliable improvements.
