Skip to content

Upgrade to Onfleet SDK 0.12.0, modernize toolchain, and add CI#2

Merged
polivmi1 merged 4 commits into
masterfrom
ci/add-build-and-best-practices
Jun 18, 2026
Merged

Upgrade to Onfleet SDK 0.12.0, modernize toolchain, and add CI#2
polivmi1 merged 4 commits into
masterfrom
ci/add-build-and-best-practices

Conversation

@polivmi1

Copy link
Copy Markdown
Member

Summary

  • Upgrade com.onfleet:driver 0.11.1 → 0.12.0 and migrate the example to the
    new API (selfAssignTasks, getTasks flow, AccountStatus.INVITED, nullable
    getters, new SDKErrorType cases, attestationAge/customRequirements).
  • Modernize the build toolchain: Gradle 9.3.1, AGP 9.1.0, Kotlin 2.1.0,
    compileSdk 36, minSdk 26, Java 21, Compose compiler plugin, Firebase BOM
    (drops MultiDex).
  • Add CI (GitHub Actions) building assembleDebug on every PR to master.
  • Add Dependabot (gradle + github-actions, weekly).
  • Make the project build out of the box: commit the Gradle wrapper, a
    non-functional placeholder google-services.json, and an
    onfleet.properties.example template (real onfleet.properties untracked).
  • Refresh the README and update the CHANGELOG for 0.12.0.

Notes

  • CI triggers on pull requests to master only — direct pushes to master
    are not allowed (branch protection to be enabled after the first green run).
  • settings.gradle keeps a commented-out mavenLocal() for future local
    testing of unreleased SDK builds; 0.12.0 resolves from Maven Central.
  • Verified locally: ./gradlew assembleDebug succeeds against the published
    0.12.0 (Gradle 9.3.1 / AGP 9.1.0 / JDK 21).

polivmi1 and others added 4 commits June 10, 2026 12:57
- Bump com.onfleet:driver to 0.12.0 and migrate the example to the new API
  (selfAssignTasks, getTasks flow, AccountStatus.INVITED, nullable getters,
  new SDKErrorType cases, attestationAge/customRequirements on completion)
- Modernize toolchain: Gradle 9.3.1, AGP 9.1.0, Kotlin 2.1.0, compileSdk 36,
  minSdk 26, Java 21, Compose compiler plugin, Firebase BOM
- Drop MultiDex (minSdk now 26) and the manual Compose compiler version
- Update settings.gradle with pluginManagement/dependencyResolutionManagement
- Refresh CHANGELOG.md with 0.12.0 notes

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Add GitHub Actions CI (.github/workflows/ci.yml) building assembleDebug on
  pull requests targeting master; direct pushes to master are not allowed, so
  there is no push trigger. JDK 21 to match the Java 21 toolchain
- Add Dependabot config (.github/dependabot.yml) for gradle + github-actions
- Commit the Gradle wrapper (gradlew, gradlew.bat, gradle-wrapper.jar) so CI
  and fresh clones can run ./gradlew; un-ignore in .gitignore
- Commit a non-functional placeholder app/google-services.json so the project
  builds out of the box; real config stays local via google-services.json.local
- Stop tracking onfleet.properties; add onfleet.properties.example template and
  ignore the local copy
- Add mavenLocal() to settings.gradle for local testing of unreleased SDK
  builds (publishToMavenLocal) before they hit Maven Central
- Refresh README with setup/build/CI instructions

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mavenLocal() was added for local testing of the unreleased 0.12.0 build.
0.12.0 is now published to Maven Central, so the example resolves it from
there; the line is kept (commented) for future pre-release local testing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 issues found across 20 files

Confidence score: 3/5

  • In app/src/main/java/com/onfleet/sdk/onfleetclientexample/OnfleetClientExampleApplication.kt, planting Timber.DebugTree() without the BuildConfig.DEBUG guard can expose verbose logs in production, which increases the chance of leaking internal/runtime details after release — restore the debug guard or use a release-safe tree before merging.
  • In README.md, the documented CI behavior (pushes to master) does not match the actual workflow trigger (PRs only), which can mislead contributors and hide unmet expectations around continuous validation — update the README or add a matching push trigger before merge.
  • In app/build.gradle.kts, keeping Compose tooling under implementation can unnecessarily increase release artifact size and ship debug-only dependencies to users — move it to debugImplementation to de-risk the release footprint.

Shadow auto-approve: would not auto-approve because issues were found.

Re-trigger cubic

Comment thread README.md
Comment thread app/build.gradle.kts
@polivmi1 polivmi1 requested a review from rSavarisOnfleet June 18, 2026 08:45
@polivmi1 polivmi1 merged commit d9e98b5 into master Jun 18, 2026
2 checks passed
@polivmi1 polivmi1 deleted the ci/add-build-and-best-practices branch June 18, 2026 13:39
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