-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: add support for chaining setups, by storing the setups in an intermediary #77
Conversation
…ntermediary Contains breaking changes to the API, but hopefully not to any usages
great, the automation re-adds it, @arunpoudel can you help |
@nhhagen Try now. |
@arunpoudel it still things 1.0.0 is the next release: https://github.com/coopnorge/go-logger/releases, but that is caused by #79 How do we resolve that |
A temporary solution for now is to remove the label and re-run release drafter from main branch. |
@nhhagen @bendiknesbo Done. I will check if we have some time to namespace our labels this tech-debt day. |
I re-ran the release drafter on main(https://github.com/coopnorge/go-logger/actions/runs/7572685129), and now the next version is v0.6.1, as expected. |
Great! |
@bendiknesbo Yes, that is how it will work. But if you want to keep the same minor version number, remove minor label, and it will treat it as a patch. |
This PR should be a minor-version bump, so I'll leave the |
Contains breaking changes to the API, but hopefully not to any usages.
Will set labels on the PR to
minor
, and commit this breaking change as allowed during v0.