- [ ] **(Optional)** Generate and deploy new update responses
-**NOTE**: This is only required if there will be no corresponding 14.0 release (i.e. this is an emergency legacy-only 13.5 release). Normally, legacy update responses are generated and deployed as part of the 14.0 release.
-**⚠️ WARNING**: This is a little bit off the beaten track, ping boklm or morgan if you have any doubts
- From the `maint-14.0` branch:
- [ ] Update `rbm.conf`
- [ ] `var/torbrowser_legacy_version`: update to `${TOR_BROWSER_VERSION}`
-**NOTE** this is the browser version for the legacy branch, not the 14.0 branch
- [ ] `var/torbrowser_legacy_platform_version`: update to `${ESR_VERSION}`
-**NOTE** this is ESR version for the legacy branch, not the 14.0 branch
- [ ] Generate update responses:
- [ ] Run:
```
make torbrowser-update_responses-release
```
- On `staticiforme.torproject.org`, deploy new update responses:
-**NOTE**: for now this is a bit janky, we should somehow update the workflow to be a bit less hacky
- [ ] Edit an existing `deploy_update_responses-release.sh` script in your `HOME` directory with the newly pushed commit hash