Skip to content

Commit

Permalink
v0.4.0: update deploy + changelog (#111)
Browse files Browse the repository at this point in the history
  • Loading branch information
tam7t authored May 24, 2021
1 parent 3dd8c1b commit a03ccbb
Show file tree
Hide file tree
Showing 3 changed files with 13 additions and 3 deletions.
12 changes: 11 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,17 @@

All notable changes to secrets-store-csi-driver-provider-gcp will be documented in this file. This file is maintained by humans and is therefore subject to error.

## unreleased (v0.4.0)
## unreleased

## v0.4.0

Images:

* `asia-docker.pkg.dev/secretmanager-csi/secrets-store-csi-driver-provider-gcp/plugin:v0.4.0`
* `europe-docker.pkg.dev/secretmanager-csi/secrets-store-csi-driver-provider-gcp/plugin:v0.4.0`
* `us-docker.pkg.dev/secretmanager-csi/secrets-store-csi-driver-provider-gcp/plugin:v0.4.0`

Digest: `sha256:d4b3b361dbf41ae407532358ec89510a20fc15d6e9620fd27f281c1e8f6db864`

### Added

Expand Down
2 changes: 1 addition & 1 deletion deploy/provider-gcp-plugin.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ spec:
serviceAccountName: secrets-store-csi-driver-provider-gcp
containers:
- name: provider
image: us-docker.pkg.dev/secretmanager-csi/secrets-store-csi-driver-provider-gcp/plugin@sha256:90eeaef1afcbac988fb9f5a96222dff91f79920e9fa1c0d4200688ebc2680622
image: us-docker.pkg.dev/secretmanager-csi/secrets-store-csi-driver-provider-gcp/plugin@sha256:d4b3b361dbf41ae407532358ec89510a20fc15d6e9620fd27f281c1e8f6db864
imagePullPolicy: IfNotPresent
resources:
requests:
Expand Down
2 changes: 1 addition & 1 deletion docs/releasing.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Notes on building a release.
gcloud builds submit --config scripts/cloudbuild-release.yaml --substitutions=_VERSION=<vX.X.X>,_BRANCH_NAME=<release-X.X> --no-source
```

4. Update `deploy/` `yaml` files to point to the content addressable sha
4. Update `deploy/` `yaml` files to point to the content addressable sha and update `CHANGELOG.md`
5. Manually test release image
6. Tag the commit from step 4 as `vX.X.X` by creating a new release
7. Merge changes from `release-X.X` into `main`
Expand Down

0 comments on commit a03ccbb

Please sign in to comment.