update-dependencies
Weekly dependency update workflow for Sesori Apps Monorepo. Updates every pubspec.yaml across the bridge and client workspaces plus standalone packages, regenerates all lockfiles, re-resolves iOS/macOS SwiftPM native dependencies (Package.resolved), updates Fastlane/Gemfile versions, handles conflicts, and verifies via analyze/test/codegen.
sesori-ai · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add sesori-ai/sesori_apps_monorepo --skill update-dependenciesAbout this skill
name: update-dependencies description: Weekly dependency update workflow for Sesori Apps Monorepo. Updates every pubspec.yaml across the bridge and client workspaces plus standalone packages, regenerates all lockfiles, re-resolves iOS/macOS SwiftPM native dependencies (Package.resolved), updates Fastlane/Gemfile versions, handles conflicts, and verifies via analyze/test/codegen.
<project_structure> The repo has two Dart workspaces and two standalone packages. Workspace members share a single resolution; standalone packages resolve independently.
Client workspace (client/pubspec.yaml is the workspace root, has flutter env constraint):
client/pubspec.yaml— workspace root, env onlyclient/module_auth/pubspec.yamlclient/module_core/pubspec.yamlclient/module_prego/pubspec.yaml(Flutter package — theme/assets)client/module_desktop_core/pubspec.yaml(pure Dart desktop business logic)client/design_catalog/pubspec.yaml(Flutter design-system catalog)client/app/pubspec.yaml(Flutter app — Firebase, flutter_bloc, etc.)client/desktop/pubspec.yaml(Flutter desktop app)
Bridge workspace (bridge/pubspec.yaml is the workspace root, pure Dart):
bridge/pubspec.yaml— workspace root, env onlybridge/sesori_plugin_interface/pubspec.yamlbridge/sesori_bridge_foundation/pubspec.yaml(depends onsesori_plugin_interface; bridge-wide shared primitives)bridge/sesori_plugin_runtime/pubspec.yaml(depends onsesori_plugin_interface)bridge/sesori_plugin_opencode/pubspec.yamlbridge/sesori_plugin_codex/pubspec.yamlbridge/sesori_plugin_acp/pubspec.yamlbridge/sesori_plugin_cursor/pubspec.yamlbridge/sesori_plugin_omp/pubspec.yamlbridge/sesori_plugin_claude/pubspec.yamlbridge/sesori_plugin_pi/pubspec.yamlbridge/sesori_plugin_hermes/pubspec.yamlbridge/app/pubspec.yaml(CLI relay server)
Standalone packages (NOT in any workspace — resolve independently with their own lockfile):
shared/sesori_shared/pubspec.yaml— pure Dart; consumed by both workspaces viapath:depshared/no_slop_linter/pubspec.yaml— pure Dart analyzer plugin; consumed bymodule_pregoviapath:dev_dep
IMPORTANT: Update shared/sesori_shared FIRST because both workspaces depend on it.
DO NOT update shared/no_slop_linter as part of this workflow. Its analyzer/_fe_analyzer_shared constraints span multiple majors intentionally and break easily — bumps are done manually, less often, by a human. Skip its pubspec edits in Phase 3, but still run make analyze/make test against it via the shared Makefile for verification.
<ios_files>
Sesori iOS is Swift Package Manager only — there is no Podfile, and CocoaPods is not part of the iOS dependency graph. Do not run pod install or attempt to add Podfile handling here.
client/app/ios/Gemfile(fastlane gem only)client/app/ios/Gemfile.lock</ios_files>
<android_files>
client/app/android/Gemfile(fastlane gem)client/app/android/Gemfile.lock</android_files>
<swiftpm_files>
iOS and macOS pull native dependencies (Firebase, Google SDKs, leveldb, gRPC, etc.) via Swift Package Manager. The resolved native versions are pinned in Package.resolved lockfiles. All four tracked copies matter — the project copy and the workspace copy, per platform:
client/app/ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolvedclient/app/macos/Runner.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolvedclient/app/ios/Runner.xcworkspace/xcshareddata/swiftpm/Package.resolvedclient/app/macos/Runner.xcworkspace/xcshareddata/swiftpm/Package.resolved
flutter build --config-only regenerates only the project copies. The Runner.xcworkspace copies are what Xcode actually consumes when a build targets the workspace — which is exactly what the iOS release lanes do (build_app(workspace: "Runner.xcworkspace", ...) in client/app/ios/fastlane/Fastfile). Leaving them stale means the shipped TestFlight/App Store build silently links the OLD native SDKs even though the PR claims to have updated them. Verified 2026-07-21: with the workspace copy stale, xcodebuild -resolvePackageDependencies -workspace Runner.xcworkspace -scheme Runner resolved AppCheck 11.3.0 / GoogleUtilities 8.1.1 while the project copy already said 11.3.1 / 8.1.2.
Both copies describe the same package graph, so after Phase 5.1 they must end up with identical pins.
These lockfiles change on most weekly runs because native SDK patch releases land continuously, independent of pubspec.yaml. They MUST be re-resolved every run (Phase 5). Use flutter build --config-only for the project copies; a bare xcodebuild -resolvePackageDependencies honors whatever pins already exist and silently no-ops, so it only re-resolves the workspace copies once their lockfile has been deleted. Skipping (or using the wrong resolve command) is a silent, recurring miss — e.g. one past run bumped firebase-ios-sdk but left GoogleUtilities/nanopb/promises stale; another run's bare xcodebuild resolve reported "no changes" while a flutter build --config-only picked up GTMSessionFetcher 4.5.0→5.3.0, GoogleUtilities 8.1.0→8.1.1, nanopb, and Promises.
</swiftpm_files>
</project_structure>