Document the 5.6.x track and where its patches come from - #95
Open
mutumbakato wants to merge 2 commits into
Open
Document the 5.6.x track and where its patches come from#95mutumbakato wants to merge 2 commits into
mutumbakato wants to merge 2 commits into
Conversation
Nutrient Flutter SDK 6.0 and later are published to pub.dev only. The native SDK APIs are reachable through the bindings API, so this repository no longer needs to carry the plugin source for new releases, and master stays on 5.6.x. Also pin the installation snippet to ^5.6.0. It read `nutrient_flutter: any`, which resolves to 6.0.0 once that is on pub.dev, while the surrounding setup instructions here are 5.6.x-era — different minimum Android API level, Flutter version, and dependency shape. Following this README with `any` would fail to build. The nightly branch continues to receive updates.
mutumbakato
changed the title
mutumbakato
marked this pull request as ready for review
August 12, 2026 17:58
New 5.6.x patch releases are published to this repository only, so a pub.dev constraint cannot deliver one. `^5.6.0` resolves to 5.6.1 and stays there, which meant this README told readers to consume 5.6.x from the one channel that will not carry its fixes. - Recommends a Git dependency pinned to a release tag, and keeps `^5.6.0` as the pub.dev option for anyone who does not need patches. - Reframes "no longer updated for newer releases", which read as abandoned, and states the December 2026 patch window. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mutumbakato
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From 6.0 onwards the Flutter SDK is published to pub.dev only — users reach the native SDK APIs through the bindings API, so this repository no longer needs to carry the plugin source for new releases.
masterstays on 5.6.x, and pre-6.0 updates land here directly via PRs. Thenightlybranch continues to receive updates.5.6.x keeps receiving patch releases here through December 2026, for projects that aren't ready to adopt the bindings API. Those patches are published to this repository only.
Changes
nutrient_flutter: anyto a Git dependency pinned to a release tag.anyresolves to 6.0.0, while every instruction around it is 5.6.x-era —minSdkVersion 21vs 24, no Flutter 3.44.6 requirement, no bindings entry point, no direct platform-package dependencies. Anyone following this README withanywould hit a build failure that looks like an SDK bug.^5.6.0resolves to 5.6.1 and stays there, since new patches don't go to pub.dev. It's kept as the documented option for anyone who doesn't need patches.Notes
5.6.1resolves on this repository, the repo root is thenutrient_flutterpackage, and itspubspec.yamlat that tag readsversion: 5.6.1.