We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As per #1683 (comment). We should also in the same file mention that version_mapping.go should be updated after each new release.
version_mapping.go
After a release, in case developer did not know which files to update.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
We should also in the same file mention that version_mapping.go should be updated after each new release.
I think it would be better that mention it in the releasing.md file.
Sorry, something went wrong.
ayildirim21
No branches or pull requests
Summary
As per #1683 (comment). We should also in the same file mention that
version_mapping.go
should be updated after each new release.Use Cases
After a release, in case developer did not know which files to update.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: