is release/next a syntax used by co-op cloud? or was that meant as a placeholder for the literal next version? @3wordchant@fauno ? I haven't seen that before, so didn't want to merge this in before confirming that
is `release/next` a syntax used by co-op cloud? or was that meant as a placeholder for the literal next version? @3wordchant @fauno ? I haven't seen that before, so didn't want to merge this in before confirming that
And then create or append to the text file release/next. This file will be used when running abra recipe release. Abra will ask you to use these when running abra recipe release and rename it to the release tag, e.g. release/1.1.0+5.9.0.
@notplantsthanks ty for the review!
Yes, `release/next` is handled:
> And then create or append to the text file release/next. This file will be used when running abra recipe release. Abra will ask you to use these when running abra recipe release and rename it to the release tag, e.g. release/1.1.0+5.9.0.
https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Looks wonderful! My only suggestion would be to add
release/nextto warn upgraders about the change.done @3wordchant @notplants
is
release/nexta syntax used by co-op cloud? or was that meant as a placeholder for the literal next version? @3wordchant @fauno ? I haven't seen that before, so didn't want to merge this in before confirming that@notplantsthanks ty for the review!
Yes,
release/nextis handled:https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-write-version-release-notes
cool, I had just been manually entering the version number before in the release/ directory.
merging now ~