Merge pull request #289 from wireapp/r2020-06-19

Release 2020-06-19

.github/ISSUE_TEMPLATE/bug-repport.md

@@ -0,0 +1,42 @@
+---
+name: Bug Report
+about: template to report a bug
+title: "Bug: [BUG TITLE]"
+labels: ''
+assignees: ''
+---
+
+### Basic information
+
+<!-- Depending on your use case some of the information might be omitted -->
+
+* On-premises: <!-- yes / no -->
+* Cloud-Provider: <!-- e.g. AWS, GCP, none, etc. -->
+* Installation type: <!-- demo / production -->
+* Kubernetes version: <!-- run 'kubectl version' -->
+* Installed with Kubespray: <!-- no / yes (version?) --> 
+* Helm chart version: <!-- Chart(s) & Version -->
+* Other related technology + version: <!-- Ansible, Helm, Terraform -->
+
+
+### What is the expected result?
+
+<!--
+Please elaborate.
+-->
+
+
+### What is the actual result?
+
+<!--
+Please elaborate.
+Add logs, outputs, if necessary.
+-->
+
+
+### How to reproduce the issue?
+
+<!--
+Please describe the steps to reproduce the actual result.
+Add a minimal example, if possible.
+-->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,40 @@
+---
+name: Feature Request
+about: Template for a question around the topic of deploying wire-server 
+title: "Feature: [FEATURE TITLE]"
+labels: ''
+assignees: ''
+---
+
+
+### What kind of feature are you looking for?
+
+<!--
+Describe the feature.
+-->
+
+
+### In which scenario would this feature be helpful?
+
+<!--
+Please describe the use case in a comprehensible manner.
+The more context you give the better we can understand the underlying issue.  
+-->
+
+
+### How do you imagine that this feature is being used?
+
+<!--
+Explain the user perspective.
+Share some example code.  
+-->
+
+
+### How did you install Wire?
+
+<!--
+In context of the proposed feature, please explain your setup a little. 
+Which installation instructions did you follow on docs.wire.com (e.g. demo / production)?
+Where and how do you run Kubernetes (operating system version and cloud provider, if any)?
+How was Kubernetes installed (e.g. Kubespray, managed, etc.)?
+-->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,37 @@
+---
+name: Question
+about: template for a question around the topic of deploying wire-server 
+title: "Question: [QUESTION TITLE]"
+labels: ''
+assignees: ''
+---
+
+### Basic information
+
+<!-- Depending on your use case some of the information might be omitted -->
+
+* On-premises: <!-- yes / no -->
+* Cloud-Provider: <!-- e.g. AWS, GCP, none, etc. -->
+* Installation type: <!-- demo / production -->
+* Kubernetes version: <!-- run 'kubectl version' -->
+* Installed with Kubespray: <!-- no / yes (version?) --> 
+* Helm chart version: <!-- Chart(s) & Version -->
+* Other related technology + version: <!-- Ansible, Helm, Terraform -->
+
+
+### How did you install Wire?
+
+<!--
+Did you deviate from the instructions one docs.wire.com at some point?
+Which operating system did you use and which version of it?  
+How did you set up TLS certificates and DNS records?
+Please explain your setup a little.
+-->
+
+
+### Question
+
+<!--
+I couldn't find an answer in the installation guide (https://docs.wire.com/how-to/install/index.html)
+nor somewhere else in the documentation (https://docs.wire.com/how-to/index.html)
+-->

.github/PULL_REQUEST_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/PULL_REQUEST_TEMPLATE/default.md

@@ -0,0 +1,61 @@
+---
+name: Change (PR)
+about: template for a PR that introduces a change 
+title: "[TITLE]"
+labels: 
+assignees:
+---
+
+<!-- In case this addressed an existing issue 
+Fixes ${ISSUE_URL}
+-->
+
+### Change type
+
+<!-- choose the kind of change this PR introduces -->
+
+* [ ] Fix
+* [ ] Feature
+
+
+### Basic information 
+
+Technology: <!-- Ansible, Kubernetes, Helm, Terraform -->
+
+Version: <!-- Version of the technologies you just referred to -->
+
+* [ ] I ran/applied the changes myself
+* [ ] I can confirm that it was successful
+
+
+### Motivation
+
+<!--
+What is the motivation for introducing this change?
+Which scenario(s) is/are addressed by the change?
+What problem does the change try to solve? 
+-->
+
+
+### Objective
+
+<!--
+What kind behaviour does it change, add, or remove?
+How did it behave before? How does it behave now? 
+-->
+
+
+### Reason
+
+<!--
+How did you fix the issue?
+Why did you solve it this way? 
+-->
+
+
+### Use case
+
+<!--
+How is the change used? maybe share some example code.
+Does the change introduce any incompatibility?
+-->

CHANGELOG.md

@@ -1,3 +1,17 @@
+# 2020-06-19
+
+## Features
+
+* Update all three frontends (webapp, team-settings, account-pages) to latest production release (#286)
+
+## Bug Fixes
+
+* Quote smsSender (#287)
+
+## Internal Changes
+
+* Add Github templates for Issues and PRs (#259, d5b16a99f0aa)
+
 # 2020-06-03
 
 ## Features

charts/account-pages/values.yaml

@@ -9,7 +9,7 @@ resources:
     cpu: "1"
 image:
   repository: quay.io/wire/account
-  tag: 2124-2.0.2-df000b-v0.24.26-production
+  tag: 4543-2.1.0-e0f7f1-v0.24.72-production
 service:
   https:
     externalPort: 443

charts/brig/templates/configmap.yaml

@@ -74,7 +74,7 @@ data:
       general:
         templateDir: /usr/share/wire/templates
         emailSender: {{ .emailSMS.general.emailSender }}
-        smsSender: {{ .emailSMS.general.smsSender }}
+        smsSender: {{ .emailSMS.general.smsSender | quote }}
         templateBranding:
           {{- with .emailSMS.general.templateBranding }}
           brand: {{ .brand }}

charts/team-settings/values.yaml

@@ -9,7 +9,7 @@ resources:
     cpu: "1"
 image:
   repository: quay.io/wire/team-settings
-  tag: 13000-2.10.0-3b12f2-v0.24.33-production
+  tag: 14965-2.12.0-9c23a0-v0.24.68-production
 service:
   https:
     externalPort: 443

charts/webapp/values.yaml

@@ -9,7 +9,7 @@ resources:
     cpu: "1"
 image:
   repository: quay.io/wire/webapp
-  tag: 48056-0.1.0-f5e9e8-v0.24.34-production
+  tag: 52663-0.1.0-b524bd-v0.24.72-production
 service:
   https:
     externalPort: 443