chore: bump to 5.0.5 to publish the Courier_iOS 5.8.6 pin - #52
Merged
Conversation
#51 bumped the podspec to Courier_iOS 5.8.6, but it merged after v5.0.4 was tagged and did not touch pubspec.yaml. The deploy job saw the tag already existed and skipped, so the published 5.0.4 still declares Courier_iOS 5.8.3 — two releases behind. This cuts the patch release that ships the pin. Also trues up example/pubspec.lock, which still recorded the path dependency at 5.0.0; it drifted across the 5.0.1–5.0.4 bumps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
What
Cuts the patch release that actually ships the
Courier_iOS 5.8.6pin.Why
#51 bumped
ios/courier_flutter.podspectoCourier_iOS 5.8.6, but it merged afterv5.0.4was tagged and it did not touchpubspec.yaml.deploy.ymlgates on whetherv$VERSIONalready exists as a tag, so that run skipped and the pin has been sitting onmainunpublished.Verified against the publish commit: the podspec at
ba13d6e(the tree that became 5.0.4 on pub.dev) declaresCourier_iOS 5.8.3, two releases behindmain.The Dart-side action click reporting from #50 works regardless — it goes through the existing
client.inbox.clickchannel method and needs no new native surface — so this is about the stale pin, not a broken feature.Changes
pubspec.yaml5.0.4 → 5.0.5.example/pubspec.lockstill recorded the path dependency at 5.0.0; it drifted across the 5.0.1–5.0.4 bumps andflutter pub gettrues it up.Verification
flutter analyze lib— no errors. The 5 remaining items are pre-existing info-level deprecation notices (withOpacity,activeColor,MaterialStateProperty,avoid_print), unchanged by this PR.🤖 Generated with Claude Code