Add NEWS for Ink 0.9.0 and bump version.
Review Request #14729 — Created Dec. 8, 2025 and submitted
This change preps Ink for a release.
| Summary | ID |
|---|---|
| qplwxmzvvvyxotvrpzvuxzoltlsnryxp |
| Description | From | Last Updated |
|---|---|---|
|
We should elaborate on what these do. Mention they're async, and that confirm dialogs can be suppressed. We don't have … |
|
|
|
Can we add () to the end so it's clear these are functions? |
|
|
|
This is missing a relative pronoun now, it should say something like "These are two new async methods that make … |
|
|
|
The second line of text isn't aligned with the first. |
|
|
|
It's not clear what this enables. We should state that consumers can see if the user wanted to suppress the … |
|
|
|
Let's elaborate on how these are improved, what they improved upon. |
|
|
|
I think this makes sense to us but I'm not sure it makes a lot of sense without a lot … |
|
|
|
It's not clear here how this simplifies things. We should mention that it's async and resolves once the dialog has … |
|
|
|
Two blank lines between sections. |
|
-
-
We should elaborate on what these do. Mention they're async, and that confirm dialogs can be suppressed. We don't have a lot of public documentation right now other than the release notes.
-
-
-
It's not clear what this enables. We should state that consumers can see if the user wanted to suppress the checkbox, and then store that in an application-specific way to determine what action to take in the future.
-
-
I think this makes sense to us but I'm not sure it makes a lot of sense without a lot of knowledge of how it worked before.
-
It's not clear here how this simplifies things. We should mention that it's async and resolves once the dialog has been closed.
-
- Commits:
-
Summary ID qplwxmzvvvyxotvrpzvuxzoltlsnryxp qplwxmzvvvyxotvrpzvuxzoltlsnryxp - Diff:
-
Revision 2 (+66 -2)