Skip to content

docs: update dependency versions to 2.8.6#3289

Open
EagleSoft461 wants to merge 2 commits into
springdoc:mainfrom
EagleSoft461:docs/update-version-to-2.8.6
Open

docs: update dependency versions to 2.8.6#3289
EagleSoft461 wants to merge 2 commits into
springdoc:mainfrom
EagleSoft461:docs/update-version-to-2.8.6

Conversation

@EagleSoft461
Copy link
Copy Markdown

What

Updated hardcoded placeholder versions (last-release-version, latest)
in README.md to the current stable release version 2.8.6.

Why

The README contained placeholder text instead of actual version numbers,
which could confuse new users trying to add the dependency.

@Mattias-Sehlstedt
Copy link
Copy Markdown
Contributor

To my understanding this version documentation would become incorrect the second a new version is released? Thus why most projects simply refer to "latest" and let you visit the repository to see what the current latest version is.

If you prefer to have a concrete version, then I would also suggest you to provide an example of how one could ensure that this is managed automatically.

@EagleSoft461
Copy link
Copy Markdown
Author

Good point! I've updated the PR to revert the hardcoded versions and instead added a Maven Central badge that always reflects the latest release automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants