* We no longer need to dispatch manually a workflow, it will wait for the publish to be approved for feature branches. * The notification template has been extracted to a variable for the repo, meaning no need to do commit push to update it! (https://github.com/sunnypilot/sunnypilot/settings/variables/actions/DISCORD_GENERAL_UPDATE_NOTICE) * The configuration for what can be auto deployed is now also a variable, no need to commit a change to update that (https://github.com/sunnypilot/sunnypilot/settings/variables/actions/AUTO_DEPLOY_PREBUILT_BRANCHES) * The configuration for what sends a message on `#dev-feedback` channel on discord is also configurable (https://github.com/sunnypilot/sunnypilot/settings/variables/actions/DEV_FEEDBACK_NOTIFICATION_BRANCHES)
openpilot releases
release checklist
Go to devel-staging
- update
devel-staging:git reset --hard origin/master-ci - open a pull request from
devel-stagingtodevel
Go to devel
- update RELEASES.md
- close out milestone
- post on Discord dev channel
- bump version on master:
common/version.handRELEASES.md - merge the pull request
tests:
- update from previous release -> new release
- update from new release -> previous release
- fresh install with
openpilot-test.comma.ai - drive on fresh install
- comma body test
- no submodules or LFS
- check sentry, MTBF, etc.
Go to release3
- publish the blog post
git reset --hard origin/release3-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 production
- Post on Discord, X, etc.