Skip to content

docs(readme): fix v3.0 release note links - #9853

Merged
hjh0119 merged 1 commit into
modelscope:mainfrom
RerankerGuo:docs/fix-v3-release-links
Aug 4, 2026
Merged

hjh0119 merged 1 commit into
modelscope:mainfrom
RerankerGuo:docs/fix-v3-release-links

Conversation

@RerankerGuo

Copy link
Copy Markdown
Contributor

PR type

  • Bug Fix
  • New Feature
  • Document Updates
  • More Models or Datasets Support

PR information

Background

The English and Chinese README timelines still link to:

docs/source_en/Instruction/ReleaseNote3.0.md
docs/source/Instruction/ReleaseNote3.0.md

Both files were deleted in #7379, so the public README links now lead to
404 pages. The official v3.0.0 GitHub Release remains published and is
the stable source for this release information.

Changes

  • Point the English ms-swift 3.0 timeline entry to the official
    v3.0.0 Release.
  • Apply the same correction to the Chinese README.
  • Keep all timeline text and other historical entries unchanged.

Verification

  • Confirmed both old local targets do not exist.
  • Confirmed https://github.com/modelscope/ms-swift/releases/tag/v3.0.0
    is a published, non-draft Release.
  • Confirmed neither README retains a ReleaseNote3.0.md reference.
  • .venv/bin/pre-commit run --all-files
  • git diff --check

Impact

Documentation only. The change repairs two public README links without
affecting code, packaging, or runtime behavior.

Experiment results

Before the change, both relative targets were absent from the repository.
After the change, both README entries resolve to the published v3.0.0
Release page.

Replace links to deleted bilingual release-note files with the published GitHub v3.0.0 Release page.

Test: pre-commit run --all-files
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@hjh0119
hjh0119 merged commit 15c97e0 into modelscope:main Aug 4, 2026
1 check passed
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