Skip to content
New issue

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

README.md: SemVer case typo #7962

Merged
merged 1 commit into from
May 16, 2023
Merged

Conversation

crisman
Copy link
Contributor

@crisman crisman commented May 16, 2023

SemVer (if we are capitalizing it) has a capital V. See the third
sub-header at
https://semver.org/#semantic-versioning-specification-semver
"Semantic Versioning Specification (SemVer)"

Update the text in Versioning section

SemVer (if we are capitalizing it) has a capital V. See the third
sub-header at
https://semver.org/#semantic-versioning-specification-semver
"Semantic Versioning Specification (SemVer)"

Update the text in Versioning section
@github-actions github-actions bot added the documentation Documentation label May 16, 2023
@dbaileychess dbaileychess merged commit 0675531 into google:master May 16, 2023
@crisman crisman deleted the SemVer_has_capital_V branch May 17, 2023 01:48
jochenparm pushed a commit to jochenparm/flatbuffers that referenced this pull request Oct 29, 2024
SemVer (if we are capitalizing it) has a capital V. See the third
sub-header at
https://semver.org/#semantic-versioning-specification-semver
"Semantic Versioning Specification (SemVer)"

Update the text in Versioning section
jochenparm pushed a commit to jochenparm/flatbuffers that referenced this pull request Oct 29, 2024
SemVer (if we are capitalizing it) has a capital V. See the third
sub-header at
https://semver.org/#semantic-versioning-specification-semver
"Semantic Versioning Specification (SemVer)"

Update the text in Versioning section
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants