Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
- build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
- ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
- docs: Documentation-only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
Has tag in common/version.go been updated or have you added bump-version label to this PR?
- No, this PR doesn't involve a new deployment, git tag, docker image tag
- Yes
Does this PR have the breaking-change label?
- No, this PR is not a breaking change
- Yes