-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
0.71 changelogs #27094
0.71 changelogs #27094
Conversation
This comment has been minimized.
This comment has been minimized.
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. But we also could add a call for feedback for #26726
Co-authored-by: Aaron Junker <[email protected]>
Note to myself: Fill in installer hashes |
Opinion on #25193? |
- Fixed a typo preventing the clean up script to run. Thanks [@Sajad-Lx](https://github.com/Sajad-Lx)! | ||
- Fixed encoding on a test file to fix running tests in some configurations. Thanks [@VisualBasist](https://github.com/VisualBasist)! | ||
- Made the GPO release assets come named with a version in the build CI output. | ||
- Added Peek and Mouse Without Borders to GitHub templates. (This was a hotfix for 0.70) |
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.
Is this really a feature of (this version of) the app?
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.
No. On the other hand, we also list repo Docs updates here as well
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.
small things
Co-authored-by: Jay <[email protected]>
@Jay-o-Way To best of my knowledge, outside of PT Contributors, we haven't seen any feedback on this topic so that is why i don't want to lean too hard on adjusting. We could have a changelog folder and put these there. And maybe then do a smaller recap of what has changed. This would enable us to still iterate on the change log together. The big reason why we adopt this approach is time savings. Creating that tight recap is surprisingly time consuming and fragile if last minute changes happen |
Co-authored-by: Niels Laute <[email protected]>
Summary of the Pull Request
PR Checklist
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed