init changie

.changes/0.7.0.md

@@ -0,0 +1,97 @@
+## v0.7.0
+### May 28, 2025
+
+IMPROVEMENTS:
+* Bump Go version to 1.24.3
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.55.6 -> v1.55.7
+  * `github.com/hashicorp/vault/sdk` v0.15.0 -> v0.17.0
+  * `golang.org/x/crypto` v0.32.0 -> v0.36.0
+  * `golang.org/x/net` v0.34.0 -> v0.38.0
+  * `golang.org/x/sys` v0.29.0 -> v0.31.0
+  * `golang.org/x/text` v0.21.0 -> v0.23.0
+
+## v0.6.0
+### Feb 12, 2025
+
+IMPROVEMENTS:
+* Bump Go version to 1.23.3
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.55.5 -> v1.55.6
+  * `github.com/hashicorp/vault/sdk` v0.13.0 -> v0.15.0
+  * `golang.org/x/crypto` v0.26.0 -> v0.32.0
+  * `golang.org/x/net` v0.28.0 -> v0.34.0
+  * `golang.org/x/sys` v0.24.0 -> v0.29.0
+  * `golang.org/x/text` v0.17.0 -> v0.21.0
+
+## v0.5.0
+### Sep 5, 2024
+
+IMPROVEMENTS:
+* Bump Go version to 1.22.6
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.53.5 -> v1.55.5
+  * `github.com/hashicorp/vault/sdk` v0.12.0 -> v0.13.0
+  * `golang.org/x/crypto` v0.21.0 -> v0.26.0
+  * `golang.org/x/net` v0.23.0 -> v0.28.0
+  * `golang.org/x/sys` v0.18.0 -> v0.24.0
+  * `golang.org/x/text` v0.14.0 -> v0.17.0
+  * `golang.org/x/tools` v0.10.0 -> v0.21.1
+  * `golang.org/x/mod` v0.11.0 -> v0.17.0
+  * `github.com/docker/docker` v24.0.9 -> v25.0.6
+  * `google.golang.org/protobuf` v1.33.0 -> v1.34.2
+  * `google.golang.org/grpc` v1.60.1 -> v1.66.0
+
+## v0.4.0
+### May 20, 2024
+
+IMPROVEMENTS:
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.50.13 -> v1.53.5
+  * `github.com/hashicorp/go-hclog` v1.6.2 -> v1.6.3
+  * `github.com/hashicorp/vault/sdk` v0.11.0 -> v0.12.0
+  * `golang.org/x/crypto` v0.17.0 -> v0.21.0
+  * `golang.org/x/net` v0.17.0 -> v0.23.0
+  * `golang.org/x/sys` v0.15.0 -> v0.18.0
+  * `github.com/docker/docker` v24.0.7 -> v24.0.9
+  * `google.golang.org/protobuf` v1.31.0 -> v1.33.0
+
+## v0.3.0
+### February 8, 2024
+
+IMPROVEMENTS:
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.49.13 -> v1.50.13
+  * `github.com/hashicorp/go-secure-stdlib/awsutil` v0.2.3 -> v0.3.0
+  * `github.com/hashicorp/vault/sdk` v0.10.2 -> v0.11.0
+
+## v0.2.3
+### August 28, 2023
+
+IMPROVEMENTS:
+* Updated dependencies:
+  * `golang.org/x/crypto` v0.6.0 -> v0.12.0
+  * `golang.org/x/net` v0.8.0 -> v0.14.0
+  * `golang.org/x/sys` v0.6.0 -> v0.11.0
+  * `golang.org/x/text` v0.8.0 -> v0.12.0
+
+## v0.2.2
+### August 28, 2023
+
+IMPROVEMENTS:
+* Updated dependencies:
+  * `github.com/aws/aws-sdk-go` v1.44.268 -> v1.44.331
+  * `github.com/hashicorp/go-secure-stdlib/awsutil` v0.2.2 -> v0.2.3
+  * `github.com/hashicorp/vault/sdk` v0.9.0 -> v0.9.2
+
+BUG FIXES:
+* Fix bug when using deprecated password field to retrieve AWS credentials [GH-53](https://github.com/hashicorp/vault-plugin-database-redis-elasticache/pull/53)
+
+## v0.2.1
+
+IMPROVEMENTS:
+* Updated dependencies:
+   * `github.com/aws/aws-sdk-go` v1.44.191 -> v1.44.268
+   * `github.com/hashicorp/go-hclog` v1.4.0 -> v1.5.0
+   * `github.com/hashicorp/go-secure-stdlib/awsutil` v0.1.6 -> v0.2.2
+   * `github.com/hashicorp/vault/sdk` v0.7.0 -> v0.9.0

.changie.yaml

@@ -0,0 +1,22 @@
+changesDir: .changes
+unreleasedDir: unreleased
+changelogPath: CHANGELOG.md
+versionExt: md
+versionFormat: '## {{.Version}} ({{.Time.Format "January 02, 2006"}})'
+kindFormat: '{{.Kind}}:'
+changeFormat: '* {{.Body}} ([#{{.Custom.Issue}}](https://github.com/hashicorp/vault-plugin-database-redis-elasticache/issues/{{.Custom.Issue}}))'
+custom:
+  - key: Issue
+    label: Issue/PR Number
+    type: int
+    minInt: 1
+kinds:
+  - label: BREAKING CHANGES
+  - label: NOTES
+  - label: FEATURES
+  - label: ENHANCEMENTS
+  - label: BUG FIXES
+newlines:
+  afterKind: 1
+  beforeKind: 1
+  endOfVersion: 2

.github/PULL_REQUEST_TEMPLATE.md

@@ -13,6 +13,7 @@ How does this change affect the user experience (if at all)?
 - [ ] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet
 - [ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
 - [ ] Backwards compatible
+- [ ] Changelog entry added. See [Updating the Changelog](https://github.com/hashicorp/vault-plugin-database-redis-elasticache/blob/main/README.md#updating-the-changelog).
 
 ## PCI review checklist
 

CHANGELOG.md

@@ -1,5 +1,3 @@
-## Unreleased
-
 ## v0.7.0
 ### May 28, 2025
 

README.md

@@ -216,3 +216,43 @@ You can also specify a `TESTARGS` variable to filter tests like so:
 ```sh
 $ make testacc TESTARGS='-run=TestConfig'
 ```
+
+
+## Updating the Changelog
+
+All pull requests that introduce a user-facing change must include a changelog
+entry. We use the [changie](https://changie.dev/) tool to manage these entries
+and automate the release process.
+
+---
+### 1. Installing Changie
+
+You only need to do this once. If you don't have `changie` installed, choose one of the options below.
+
+* **Homebrew** (macOS):
+    ```shell
+    brew install changie
+    ```
+* **Go Install**:
+    ```shell
+    go install github.com/miniscruff/changie@latest
+    ```
+* **Other Methods**:
+  See the [official changie installation guide](https://changie.dev/guide/installation/) for other options, including pre-compiled binaries.
+
+---
+### 2. Creating an Entry
+
+Once your code changes are complete, create the changelog entry:
+
+1.  **Run the command** in your terminal:
+    ```shell
+    changie new
+    ```
+2.  **Follow the prompts.** An interactive prompt will ask you to select the
+    kind of change (e.g., `BREAKING CHANGES`, `NOTES`, `FEATURES`) and write a concise description of
+    what you changed.
+
+3.  **Commit the new file.** After you're done, `changie` will create a new
+    YAML file in the `.changie/unreleased` directory. Commit this file along with your other
+    code changes before submitting your pull request.