Create a release
A release records the installed baseline that future Dart patches target. First complete the fresh-computer quick start. Work from the initialized project root.
Create the baseline
Section titled “Create the baseline”Set a unique pubspec.yaml version (example: 1.0.0+1), commit source/lockfile and configure valid signing. Select your target explicitly:
Android defaults to AAB; get-apks generates test APKs from the registered baseline. iOS requires macOS/Xcode; development is for provisioned test devices. Store releases require your normal release/distribution signing. Use the artifact path actually reported by the CLI.
Distribute the same artifact
Section titled “Distribute the same artifact”Distribute the actual pw release output to the store or device. Do not rebuild it with flutter build: that can omit the updater or differ from the registered baseline. Test signatures are not production signatures. Keep source commit, release version, package ID, signing certificate and artifact hashes.
Inspect and continue
Section titled “Inspect and continue”Inspect the same app/release in the console, install the baseline once and check normal interaction before publishing a patch. Publishing does not automatically submit your app to a store.