morgan pushed to branch main at The Tor Project / Applications /
tor-browser-build
Commits:
344327b6 by Nicolas Vigier at 2024-10-29T21:19:49+00:00
Update release prep issue templates (Tor Browser Legacy)
Add missing step when manually deploying update responses for
legacy-only release.
- - - - -
1 changed file:
- .gitlab/issue_templates/Release Prep - Tor Browser Legacy.md
Changes:
=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Legacy.md
=====================================
@@ -251,6 +251,22 @@ popd
```bash
make torbrowser-update_responses-release
```
+ - [ ] Commit new update responses to tor-browser-update-responses.git:
+ - [ ] Run:
+ ```bash
+ updaterespdir=/path/to/tor-browser-update-responses.git
+ cp
torbrowser/release/update-responses/update-responses-release-${TOR_BROWSER_VERSION}.tar
"$updaterespdir"
+ cd "$updaterespdir"
+ git pull
+ rm -Rf update_3/release
+ tar -C update_3 update-responses-release-${TOR_BROWSER_VERSION}.tar
+ rm update-responses-release-${TOR_BROWSER_VERSION}.tar
+ git add update_3/release
+ git commit -m "release: new version, ${TOR_BROWSER_VERSION}"
+ git push
+ # print the commit hash and copy past it for the next step
+ git show -s --format=%H
+ ```
- 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
View it on GitLab:
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/344327b631c00a2bd639d5a6c15f6a296800cef2
--
View it on GitLab:
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/344327b631c00a2bd639d5a6c15f6a296800cef2
You're receiving this email because of your account on gitlab.torproject.org.
_______________________________________________
tbb-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-commits
