-
-
Notifications
You must be signed in to change notification settings - Fork 899
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
docs: Release procedure documentation #1649
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent! LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments that I atleast want some clarity on, LGTM apart from that tho
CONTRIBUTING.md
Outdated
- Search through the codebase for `@Deprecated` methods/fields and remove the ones that are marked | ||
for removal in the version that you are intending to release. | ||
- Create a PR containing the changes for removing the deprecated entities. | ||
- Run `melos version -V <package>:<version> -V <package>:<version>` for Melos to generate a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Twice the -V
? Is it meant to be current vs next? If so we we should make that more explicit in the command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Twice the -V?
Yes, once for each package, and the version is the version for that package. Would it be more clear if I wrote it like this?
- Run `melos version -V <package>:<version> -V <package>:<version>` for Melos to generate a | |
- Run `melos version -V <package1>:<version> -V <package2>:<version>` for Melos to generate a |
Co-authored-by: Jochum van der Ploeg <jochum.vanderploeg@verygood.ventures>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one small nit
Adds documentation about the release procedure and breaking changes.
Description
Just adds documentation about the release procedure and breaking changes.
Checklist
fix:
,feat:
,docs:
etc).docs
and added dartdoc comments with///
.examples
.Breaking Change