You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two action github repositories in the JupyterHub org where we have ended up using another GitHub action to automatically update a vX (v1, v2 etc) branch whenever we create a GitHub Release.
At this point, perhaps it would make sense to cut a 1.0.0 release which would allow users to reference @v1 and give this repo some flexibility of managing breaking and non-breaking changes.
We have two action github repositories in the JupyterHub org where we have ended up using another GitHub action to automatically update a vX (v1, v2 etc) branch whenever we create a GitHub Release.
At this point, perhaps it would make sense to cut a 1.0.0 release which would allow users to reference
@v1
and give this repo some flexibility of managing breaking and non-breaking changes.I'd warmly recommend:
What do you think about this @jacobtomlinson?
The text was updated successfully, but these errors were encountered: