[tbb-commits] [builders/tor-browser-build] branch maint-11.0 updated: Bug 40319: Add build tag to downloads.json

[gitolite role]

This is an automated email from the git hooks/post-receive script.

boklm pushed a commit to branch maint-11.0
in repository builders/tor-browser-build.

The following commit(s) were added to refs/heads/maint-11.0 by this push:
     new bf65f0b  Bug 40319: Add build tag to downloads.json
bf65f0b is described below

commit bf65f0b797f9aeae59b900711231523f84b715b6
Author: Georg Koppen <gk at torproject.org>
AuthorDate: Fri Jun 25 20:28:37 2021 +0000

    Bug 40319: Add build tag to downloads.json
---
 projects/release/update_responses_config.yml | 1 +
 tools/update-responses/update_responses      | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/projects/release/update_responses_config.yml b/projects/release/update_responses_config.yml
index 8b3e4ff..49e692d 100644
--- a/projects/release/update_responses_config.yml
+++ b/projects/release/update_responses_config.yml
@@ -50,6 +50,7 @@ versions:
         win64:
             minSupportedOSVersion: 6.1
 mar_compression: xz
+tag: 'tbb-[% c("var/torbrowser_version") %]-[% c("var/torbrowser_build") %]'
 htaccess_rewrite_rules:
     alpha: |
         # bug 26569: Redirect pre-8.0a9 alpha users to a separate update directory
diff --git a/tools/update-responses/update_responses b/tools/update-responses/update_responses
index e897563..7881205 100755
--- a/tools/update-responses/update_responses
+++ b/tools/update-responses/update_responses
@@ -424,8 +424,10 @@ sub write_downloads_json {
     @channels = keys %{$config->{channels}} unless @channels;
     foreach my $channel (@channels) {
         my $version = $config->{channels}{$channel};
+        my $tag = get_config($config, $version, 'any', 'tag');
         my $data = {
             version => $version,
+            tag => $tag,
             downloads => get_version_downloads($config, $version),
         };
         write_htdocs($channel, 'downloads.json',

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.