- [ ] **(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.
-**NOTE**: This is only required if there will be no corresponding 15.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 15.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.5` branch:
- From the `maint-15.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
-**NOTE** this is the browser version for the legacy branch, not this stable branch we've switched to
- [ ] `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:
-**NOTE** this is ESR version for the legacy branch, not this stable branch we've switched to
- [ ] Generate update responses and commit them to tor-browser-update-responses.git:
- Run:
```bash
make torbrowser-update_responses-release
```
- [ ] Commit new update responses to tor-browser-update-responses.git: