Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 206
    • Issues 206
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #40707
Closed
Open
Issue created Dec 07, 2022 by Richard Pospesel@richardOwner

Update update_responses_config.yml to allow 11.5.8 to update to whatever latest is

So as a stop-gap to get 12.0 out, we added a set of RewriteRules to the update_pre12.0 .htaccess which redirects users to a locally copied set of 12.0 XMLs. With the current rules in place, users will need update from pre-11.5.8 -> 11.5.8 -> 12.0 -> latest. We need to update the generated .htaccess rules to migrate 11.5.8 to latest.

We should also remove the stop-gap rules in update_pre12.0 on staticiforme once the script to generate the .htaccess is updated.

Edited Dec 07, 2022 by Richard Pospesel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking