docs: fix broken PyPI link to changelog#1434
Merged
Merged
Conversation
roskakori
changed the title
Contributor
Author
|
I just checked all the "n/a" in the PR completion checklist because I cannot address them. If this is what your bots need to take this serious, so be it. |
codejedi365
merged commit 05f897f
into
python-semantic-release:master
7 of 9 checks passed
Contributor
🎉 This PR has been published as part of v10.6.0 🎉You can find more information about this release on the GitHub Releases page. |
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
2 participants
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.
Purpose
Fix link on PyPI.
Rationale
On the PyPI page, the "changelog" link pointed to a 404 because it assumed Markdown instead of reSTructred text.
How did you test?
I can't really, this need to be published on PyPI.
How to Verify
Expected result: Shows changelog instead of 404.
PR Completion Checklist
Reviewed & followed the Contributor Guidelines
Changes Implemented & Validation pipeline succeeds ❌ Can't, see comment above.
Commits follow the Conventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)
Appropriate Unit tests added/updated ❌ n/a
Appropriate End-to-End tests added/updated ❌ n/a
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines) ❌ It's a docs fix.