Skip to content

chore: release core 1.1.13 and plugin_idfa 1.0.3 (SPM fixes) - #219

Merged
MichaelGHSeg merged 3 commits into
mainfrom
release/core-1.1.13
Oct 8, 2026
Merged

MichaelGHSeg merged 3 commits into
mainfrom
release/core-1.1.13

Conversation

@MichaelGHSeg

@MichaelGHSeg MichaelGHSeg commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Releases segment_analytics 1.1.13 and segment_analytics_plugin_idfa 1.0.3, mainly to ship working Swift Package Manager support.

What's in the release

Already on main: #213, #218, #215, #197. This PR adds the rest.

Tested locally

  • Flutter 3.29.2 (Dart 3.7, devbox): core analyze clean, 127 tests pass, resolves flutter_fgbg 0.7.1. idfa analyze clean.
  • Flutter 3.47.6 (Dart 3.13), SPM enabled, no CocoaPods installed, throwaway app with path deps on core + idfa:
    • resolves flutter_fgbg 0.8.0
    • Flutter's generated plugin package picks up core, idfa and fgbg as Swift packages from the new layouts
    • flutter build macos succeeds
    • flutter build ios --simulator succeeds; AnalyticsPlugin, PluginIdfaPlugin and FGBGPlugin are linked, with no Podfile or Pods
    • Launched on an iOS 26.4 simulator: core's native getContext returns (os=iOS 26.4.1), and idfa's channel is registered and answering (blocked on the ATT prompt, as expected)
  • flutter pub publish --dry-run: 0 warnings for both packages.

Not tested locally: Android (no SDK here), the CocoaPods path. CI doesn't build native code for any platform, so these are the only native checks.

After merge

Publish manually as with 1.1.12: flutter pub publish in packages/core, then packages/plugins/plugin_idfa. publish.yml can't publish to pub.dev yet; that's separate follow-up work.

Same restructure as core in #213: Package.swift moves to
ios/segment_analytics_plugin_idfa/ with sources under
Sources/segment_analytics_plugin_idfa/, depending on FlutterFramework.
Podspec and pigeon output paths follow.
@MichaelGHSeg
MichaelGHSeg merged commit e8305f3 into main Oct 8, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants