Skip to content
This repository has been archived by the owner on Dec 1, 2023. It is now read-only.

Please tag a new release #19

Closed
josegonzalez opened this issue Jan 7, 2021 · 2 comments
Closed

Please tag a new release #19

josegonzalez opened this issue Jan 7, 2021 · 2 comments

Comments

@josegonzalez
Copy link

The only real change is the logging output, which is actually a nice change :)

@edmorley
Copy link
Member

edmorley commented Jan 7, 2021

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

@edmorley edmorley closed this as completed Jan 7, 2021
@josegonzalez
Copy link
Author

<3 Thanks it is definitely appreciated :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants