chore: release v8.0.0 #149
Conversation
WalkthroughThe changes update the changelog and package version to reflect the stable 8.0.0 release. The changelog documents the removal of the Changes
Possibly related PRs
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
CHANGELOG.md(1 hunks)pubspec.yaml(1 hunks)
🔇 Additional comments (2)
pubspec.yaml (1)
2-2: Approve version bump
The package version has been correctly updated from8.0.0-rc.1to8.0.0, matching the intended stable release.CHANGELOG.md (1)
1-2: Approve new release header
The# 8.0.0header is correctly added at the top of the changelog to denote the stable release section.
| - chore: release 8.0.0-rc.1 | ||
| - fix: remove `omit_obvious_property_types` as it conflicts with `type_annotate_public_apis` [148](https://github.com/VeryGoodOpenSource/very_good_analysis/pull/148) | ||
|
|
There was a problem hiding this comment.
Fix release entry under stable version
Under the # 8.0.0 heading, the chore entry still references the release candidate. It should reflect the stable version release.
Apply this diff:
- chore: release 8.0.0-rc.1
+ chore: release 8.0.0📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - chore: release 8.0.0-rc.1 | |
| - fix: remove `omit_obvious_property_types` as it conflicts with `type_annotate_public_apis` [148](https://github.com/VeryGoodOpenSource/very_good_analysis/pull/148) | |
| - chore: release 8.0.0 | |
| - fix: remove `omit_obvious_property_types` as it conflicts with `type_annotate_public_apis` [148](https://github.com/VeryGoodOpenSource/very_good_analysis/pull/148) |
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 3 to 5, the release entry under the stable version
heading # 8.0.0 incorrectly references the release candidate 8.0.0-rc.1. Update
the chore entry to reflect the stable version release by changing "release
8.0.0-rc.1" to "release 8.0.0" to accurately represent the stable release.
|
Maybe #151 could be included? 😇 |
Only if it works on the previous Flutter stable, otherwise it will go into the v9. We want v8 to be compatible with the previous latest stable to ensure a smoother upgrade pipeline. |
Status
READY
Description
Release v8.0.0
Type of Change
Summary by CodeRabbit
omit_obvious_property_typesfeature due to a conflict with another feature.