Please tag a new release
josegonzalez opened this issue · 2 comments
josegonzalez commented
The only real change is the logging output, which is actually a nice change :)
edmorley commented
Hi! Sure happy to :-)
For most buildpacks the tag is created at the time they are pushed to the buildpack registry, but since this buildpack isn't on the registry, that didn't occur. (Most people using the GitHub URLs on the platform will use the default branch.)
I've tagged current master
as v1.0.1
, given (a) the previous tag was v1.0.0
(most other buildpacks use integer versioning instead), (b) with the various reverts the only change is logging/readme/licence, so a patch bump only seems appropriate semver wise:
v1.0.0...v1.0.1
josegonzalez commented
<3 Thanks it is definitely appreciated :)