update release.md with changelog step

Author: m-Bilal

Diff for: release.md

@@ -7,5 +7,6 @@ The NDC Open API Lambda Connector uses GitHub Releases for release management.
 1. Use Git Tags for release. Tags should be in the format of Semver: `vMajor.Minor.Patch`. Release branches should have the format `release/{version}`. Add this tag value to the `version` field of the CLI [here](https://github.com/hasura/ndc-open-api-lambda/blob/23976ae2459c8dd0506c7d39385d5b5bd0d1e131/src/cli/index.ts#L8)
 2. Publish a Docker Image to GHCR with the name `ghcr.io/hasura/ndc-open-api-lambda` and the version tagged with the Git Tag. More on [GHRC](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry)
 3. Add the tagged version of the Docker Image in the `update` command of the connector-metadata [here](https://github.com/hasura/ndc-open-api-lambda/blob/bea1d291c56093cf0caf070ddaa0af2b3e4850a3/connector-definition/.hasura-connector/connector-metadata.yaml#L17)
-4. Create .tgz file of `connector-definition` using the command `tar -czf connector-definition.tgz connector-definition` (MacOS)
-5. Create a GitHub Release and add the .tgz file as an asset
+4. Update [Changelog](./changelog.md)
+5. Create .tgz file of `connector-definition` using the command `tar -czf connector-definition.tgz connector-definition` (MacOS)
+6. Create a GitHub Release and add the .tgz file as an asset