[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [Git][tpo/applications/tor-browser-build][main] Update release prep issue templates (Tor Browser Legacy)



Title: GitLab

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:

Changes:

  • .gitlab/issue_templates/Release Prep - Tor Browser Legacy.md
    ... ... @@ -251,6 +251,22 @@ popd
    251 251
             ```bash
    
    252 252
             make torbrowser-update_responses-release
    
    253 253
             ```
    
    254
    +    - [ ] Commit new update responses to tor-browser-update-responses.git:
    
    255
    +      - [ ] Run:
    
    256
    +        ```bash
    
    257
    +        updaterespdir=/path/to/tor-browser-update-responses.git
    
    258
    +        cp torbrowser/release/update-responses/update-responses-release-${TOR_BROWSER_VERSION}.tar "$updaterespdir"
    
    259
    +        cd "$updaterespdir"
    
    260
    +        git pull
    
    261
    +        rm -Rf update_3/release
    
    262
    +        tar -C update_3 update-responses-release-${TOR_BROWSER_VERSION}.tar
    
    263
    +        rm update-responses-release-${TOR_BROWSER_VERSION}.tar
    
    264
    +        git add update_3/release
    
    265
    +        git commit -m "release: new version, ${TOR_BROWSER_VERSION}"
    
    266
    +        git push
    
    267
    +        # print the commit hash and copy past it for the next step
    
    268
    +        git show -s --format=%H
    
    269
    +        ```
    
    254 270
       - On `staticiforme.torproject.org`, deploy new update responses:
    
    255 271
         - **NOTE**: for now this is a bit janky, we should somehow update the workflow to be a bit less hacky
    
    256 272
         - [ ] Edit an existing `deploy_update_responses-release.sh` script in your `HOME` directory with the newly pushed commit hash
    

  • _______________________________________________
    tor-commits mailing list
    tor-commits@xxxxxxxxxxxxxxxxxxxx
    https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits