Bump wp to 2.1.12 to fix deployment upgrade issue

charts/wordpress/latest/Chart.yaml

 name: wordpress
-version: 2.1.11
+version: 2.1.12
 appVersion: 4.9.8
 description: Web publishing platform for building blogs and websites.
 icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png

charts/wordpress/latest/app-readme.md

@@ -4,4 +4,7 @@
 
 This chart bootstraps a [WordPress](https://github.com/bitnami/bitnami-docker-wordpress) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. The chart also packages the [Bitnami MariaDB chart](https://github.com/kubernetes/charts/tree/master/stable/mariadb) to provide the backend database for the WordPress application.
 
-Notes: MariaDB has been configured as a StatefulSet, and it will provision PersistentVolume dynamically using VolumeClaimTemplate. Users can use the existing Persistent Volume by creating PVC with name i.e. `data-wordpress-mariadb-0`
+## Notes: 
+MariaDB has been configured as a StatefulSet, and it will provision PersistentVolume dynamically using VolumeClaimTemplate. Users can use the existing Persistent Volume by creating PVC with name i.e. `data-wordpress-mariadb-0`
+
+Upgrade from template version 2.1.10 or 2.1.11 to the current version 2.1.12 requires a user to select `Delete and recreate resources if needed during the upgrade` option.

charts/wordpress/latest/templates/deployment.yaml

-apiVersion: apps/v1beta1
+apiVersion: apps/v1beta2
 kind: Deployment
 metadata:
   name: {{ template "fullname" . }}
@@ -9,11 +9,14 @@ metadata:
     heritage: "{{ .Release.Service }}"
 spec:
   replicas: {{ .Values.replicaCount }}
+  selector:
+    matchLabels:
+      app: {{ template "fullname" . }}
+      release: "{{ .Release.Name }}"
   template:
     metadata:
       labels:
         app: {{ template "fullname" . }}
-        chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
         release: "{{ .Release.Name }}"
     spec:
       {{- if .Values.image.pullSecrets }}