chore: prepare for v1.0.0 release (#1097)

Makefile

@@ -473,7 +473,7 @@ e2e-build-local-ratify-image:
 	kind load docker-image --name kind localbuild:test
 
 e2e-helmfile-deploy-released-ratify:
-	curl -L https://raw.githubusercontent.com/deislabs/ratify/main/helmfile.yaml | ./.staging/helmfilebin/helmfile sync -f - 
+	./.staging/helmfilebin/helmfile sync -f git::https://github.com/deislabs/ratify.git@helmfile.yaml
 
 e2e-helm-deploy-ratify:
 	printf "{\n\t\"auths\": {\n\t\t\"registry:5000\": {\n\t\t\t\"auth\": \"`echo "${TEST_REGISTRY_USERNAME}:${TEST_REGISTRY_PASSWORD}" | tr -d '\n' | base64 -i -w 0`\"\n\t\t}\n\t}\n}" > mount_config.json

charts/ratify/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: ratify
 description: A Helm chart for Ratify
-version: 1.10.0
-appVersion: v1.0.0-rc.8
+version: 1.11.0
+appVersion: v1.0.0
 home: https://github.com/deislabs/ratify

charts/ratify/values.yaml

@@ -1,7 +1,7 @@
 image:
   repository: ghcr.io/deislabs/ratify
   crdRepository: ghcr.io/deislabs/ratify-crds
-  tag: v1.0.0-rc.8
+  tag: v1.0.0
   pullPolicy: IfNotPresent
 
 nameOverride: ""
@@ -121,7 +121,7 @@ logger:
     traceIDHeaderName: # List of headers that include the trace ID in the external data requests to Ratify. The same headers will be passed to upstream services like remote registries.
       - "" # e.g. Set it to `x-ms-correlation-request-id` to trace across Azure.
 
-# See https://github.com/deislabs/ratify/blob/main/docs/reference/usage.md for a list of available feature flags
+# See https://ratify.dev/docs/1.0/reference/usage#feature-flags for a list of available feature flags
 featureFlags:
   # RATIFY_FEATURE_NAME: true