Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Release 0.11.0 #102

Merged
merged 2 commits into from
Aug 31, 2023
Merged

Release 0.11.0 #102

merged 2 commits into from
Aug 31, 2023

Conversation

dcoles
Copy link
Collaborator

@dcoles dcoles commented Aug 29, 2023

I think it's about time we cut a new release (we're about 6 months behind the upstream flipperzero-firmware project).

I'm not opposed to doing smaller point releases for new features while still maintaining the same SDK compatibility.

@dcoles dcoles force-pushed the release-0.11.x branch 2 times, most recently from d706079 to 0413596 Compare August 29, 2023 05:03
@str4d
Copy link
Contributor

str4d commented Aug 29, 2023 •
edited
Loading

I see you've ACKed #74; do you want to include it in this release (merging that PR before this one), or leave it to after (in which case I'll need to rebase it after this PR merges, to alter the correct part of the changelog)?

str4d
str4d approved these changes Aug 29, 2023
View reviewed changes
Copy link
Contributor

@str4d str4d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK; the changes for the release look correct (I checked against prior release commits).

@dcoles
Copy link
Collaborator Author

dcoles commented Aug 30, 2023

I see you've ACKed #74; do you want to include it in this release (merging that PR before this one), or leave it to after (in which case I'll need to rebase it after this PR merges, to alter the correct part of the changelog)?

Sure. Let's get that it. It's easy enough to rebase this branch prior to merging/tagging.

@str4d
Copy link
Contributor

str4d commented Aug 30, 2023

I see you've ACKed #74; do you want to include it in this release (merging that PR before this one), or leave it to after (in which case I'll need to rebase it after this PR merges, to alter the correct part of the changelog)?

Sure. Let's get that it. It's easy enough to rebase this branch prior to merging/tagging.

I merged #74 yesterday. I think it's technically not necessary to rebase this PR as long as the release is done from the main branch post-merge, but probably safer to rebase it.

@str4d
Copy link
Contributor

str4d commented Aug 30, 2023

It would be nice to get #92 in as well, but I won't have time to review it before the weekend.

@dcoles dcoles merged commit c667301 into main Aug 31, 2023
7 of 9 checks passed
@dcoles
Copy link
Collaborator Author

dcoles commented Aug 31, 2023

Tagged v0.11.0 and released on crates.io.

@str4d str4d deleted the release-0.11.x branch August 31, 2023 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JarvisCraft JarvisCraft JarvisCraft approved these changes

@str4d str4d str4d approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@dcoles @str4d @JarvisCraft