shorebird patch takes --track as an optional input. This can currently only be used with the action by passing --track stable as general build args.
Similarly, shorebird patch takes a --releases parameter. The --help output says:
-p, --platforms The platform(s) to to build this release for.
I understand that this means that I can issue a single shorebird patch command to create patches for both Android and iOS at the same time. With my current pipeline I run both patches separately, which for some reason leads Shorebird to give me different patch versions for Android and iOS (Android runs first so it gets patch number 1 and then the iOS patch gets number 2).
Maybe I am using the patch wrong. I can provide a PR with the track, but maybe someone can weigh in on the platform thing, if I am misunderstanding the documentation here.
shorebird patchtakes--trackas an optional input. This can currently only be used with the action by passing--track stableas general build args.Similarly,
shorebird patchtakes a--releasesparameter. The--helpoutput says:I understand that this means that I can issue a single
shorebird patchcommand to create patches for both Android and iOS at the same time. With my current pipeline I run both patches separately, which for some reason leads Shorebird to give me different patch versions for Android and iOS (Android runs first so it gets patch number 1 and then the iOS patch gets number 2).Maybe I am using the
patchwrong. I can provide a PR with thetrack, but maybe someone can weigh in on the platform thing, if I am misunderstanding the documentation here.