NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev · #3400 most downloaded on pub.dev
iOS platform implementation of update_available
Last release 8 months ago
28 Jan 2026
Release timing varies
gaps range from 3 weeks to 10 months
Nearly every release is documented
notes for 17 of 17 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
23 releases · first in 2020
One column per quarter.
Relax dependencies constraints (@akshaynexus)
Bust iTunes cache when fetching the published plugin version (fixes #45)
Signed-off-by: Mateus Felipe C. C. Pinto mateusfccp@gmail.com
Signed-off-by: Mateus Felipe C. C. Pinto mateusfccp@gmail.com
Nothing published for this version
Support package_info_plus: '>=4.0.2 <9.0.0'
package_info_plus: '>=4.0.2 <9.0.0'Signed-off-by: Mateus Felipe C. C. Pinto mateusfccp@gmail.com
Signed-off-by: Mateus Felipe C. C. Pinto mateusfccp@gmail.com
package_info_plus: ^5.0flutter_lints to ^3.0.1UpdateAvailableIosPlugin can't be implemented, extended or mixed anymore
UpdateAvailableIosPlugin can't be implemented, extended or mixed anymorehttp removed from the dependenciesNothing published for this version
Nothing published for this version
Nothing published for this version
Bump versions, update changelogs
Bump versions, update changelogs
Also add the changelogs and warning to the android package
Also add the changelogs and warning to the android package
Use federated plugin structure for iOS
Bump versions do dev so it doesn't fail
Create main.yml
Test
Fix line size to formatter
Bump versions do dev so it doesn't fail
Copy the checks for all folders
Fix main.yaml
Migrate to package_info_plus Address review comments
Migrate to package_info_plus
Address review comments
package_info, which is deprecated, with package_info_plusDisclaimer: I think that it's correctly working, but as I am not using *null-safety* in production yet, I couldn't properly test it. @ashishbeck think
Disclaimer: I think that it's correctly working, but as I am not using null-safety in production yet, I couldn't properly test it. @ashishbeck thinks it's OK to be published as stable, so I am doing it. If you find any issue, please report.
Disclaimer: I think that it's correctly working, but as I am not using *null-safety* in production yet, I couldn't properly test it. I am going to ask
version to pub_semverDisclaimer: I think that it's correctly working, but as I am not using null-safety in production yet, I couldn't properly test it. I am going to ask to someone to test it for me and, as soon it's safe to be used in production, I publish it as stable.
- Remove pubspec.lock
- Add platform to pubspec.yaml
- Update README.md
Revert changes on pubspec.yaml, as pub.dev won't accept a plugin declaration without native integration
pubspec.yaml, as pub.dev won't accept a plugin declaration without native integration- Fix typo on documentation
- Initial version
Your coding agent can read these notes before it upgrades. Set up the MCP server →