mirror of https://github.com/firestar5683/StarPilot.git synced 2026-10-28 00:53:45 +08:00

Files

T

firestar5683 694b460f80 Developer Tools

Provide laptop and device build entry points, cache compatibility checks and developer tooling. Keep distribution assets and model packaging available before runtime consumers.

Co-authored-by: Danny <dannyirwin31@yahoo.com>
Co-authored-by: Prabhaav Pillai <prabhaav@msu.edu>
Co-authored-by: dirwin31 <83434411+dirwin31@users.noreply.github.com>
Co-authored-by: firestarsdog <229254897+firestarsdog@users.noreply.github.com>

Co-authored-by: prabhaavp <prabhaav@msu.edu>

2026-10-14 20:02:39 -05:00

tests

Developer Tools

2026-10-14 20:02:39 -05:00

build_manifest.py

2026-10-14 19:56:17 -05:00

build_release.sh

Developer Tools

2026-10-14 20:02:39 -05:00

build_stripped.sh

Developer Tools

2026-10-14 20:02:39 -05:00

check_file_sizes.sh

Remove model chunking and use LFS for Chestnut releases (#38941 )

2026-09-17 16:34:52 -07:00

check-dirty.sh

2026-10-14 19:56:17 -05:00

identity.sh

move some tools back to root (#38235 )

2026-06-24 19:21:19 -07:00

pack.py

move some tools back to root (#38235 )

2026-06-24 19:21:19 -07:00

README.md

Developer Tools

2026-10-14 20:02:39 -05:00

release_files.py

2026-10-14 19:56:17 -05:00

stage_mapd_provider.py

Developer Tools

2026-10-14 20:02:39 -05:00

README.md

Release builds

Run ./build --mapd in the source checkout before assembling a release. Both release scripts validate and include the generated Mapd executable and manifest; missing or stale packages stop assembly. Regenerate the package when Mapd source or its upstream pin changes. The generated files stay out of the source branch.

openpilot releases

## release checklist

### Go to staging
- [ ] make a GitHub issue to track release with this checklist
- [ ] create release master branch
  - [ ] create a branch from upstream master named `zerotentwo` for release `v0.10.2`
  - [ ] revert risky commits (double check with autonomy team)
  - [ ] push the new branch
- [ ] push to staging:
  - [ ] make sure you are on the newly created release master branch (`zerotentwo`)
  - [ ] run `BRANCH=devel-staging tools/release/build_stripped.sh`. Jenkins will then automatically build staging on device, run `test_onroad` and update the staging branch
- [ ] bump version on master: `openpilot/common/version.h` and `RELEASES.md`
- [ ] post on Discord, tag `@release crew`

### Go to release
- [ ] before going to release, test the following:
  - [ ] update from previous release -> new release
  - [ ] update from new release -> previous release
  - [ ] fresh install with `openpilot-test.comma.ai`
  - [ ] drive on fresh install
  - [ ] no submodules; only the Chestnut big driving model uses LFS
  - [ ] check MTBF, etc.
  - [ ] stress test passes in production
- [ ] publish the blog post
- [ ] `git reset --hard origin/release-mici-staging`
- [ ] tag the release: `git tag v0.X.X <commit-hash> && git push origin v0.X.X`
- [ ] create GitHub release
- [ ] final test install on `openpilot.comma.ai`
- [ ] update factory provisioning
- [ ] close out milestone and issue
- [ ] post on Discord, X, etc.