docs: replace invalid v0.7.0 release notes URL with GitHub docs link for consistency#1811
Open
B-X-Y wants to merge 1 commit intounclecode:developfrom
Open
docs: replace invalid v0.7.0 release notes URL with GitHub docs link for consistency#1811B-X-Y wants to merge 1 commit intounclecode:developfrom
B-X-Y wants to merge 1 commit intounclecode:developfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes an invalid URL for the v0.7.0 release notes in the
README.md.The previous link (https://docs.crawl4ai.com/blog/release-v0.7.0) returns a 404 ("The page you requested could not be found.").
This PR updates the link to the corresponding GitHub documentation page and keeps the release notes links consistent with the style used for other versions.
List of files changed and why
README.md– Updated the v0.7.0 release notes link to the GitHub docs path because the previous docs site URL returns a 404.How Has This Been Tested?
Checklist: