-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release #201
Comments
I'm clandestinely waiting for https://github.com/jmgilman/cocogitto-pr, which is clandestinely waiting for But as soon as that's in place, we should be able to do this rather swiftly. |
Deliberate dependency on #121 |
Its not a hard dependency though right? The cocogitto PR action just adds a nice preview of the changelog. Not sure why that would block a release. |
No, deliberate. To properly exercise the process and ritual. It also puts stretchy time bounds on the cocogitto-pr milestone. |
I agree it shouldn't be a hard dependency. It's possible to integrate cocogitto without the existence of the PR generation, which is really just a nicety in the end. |
Another aspect, I didn't mention, but had in mind is to land a release of If we package this properly, it can be a true milestone for the project (not just a release). |
Let me actually transform this into a milestone via Github Settings. Closing here. I'll do that tomorrow. |
We need to cut a release. We have divnix/std-action now and we need to provide some level of interoperability between the two. We can't do that to any level of sanity without tracking a stable target. It doesn't have to be 1.0 but we need to cut something. x-ref: divnix/std-action#17
The text was updated successfully, but these errors were encountered: