Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

problem with release notes link on front page

Open
#1 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
documentation

Research direction

Locate the front-page HTML source containing the release notes link and inspect its current branch target. Compare the intended stable v0.19.x destination with the main-branch alternative, then verify that the finished link opens the current release notes.

Written by the indexing model from the issue text.

Description

The "release notes" link as in the screenshot below points to the "master" branch rather than the stable v0.19.x branch. At minimum, the "master" in the link is outdated and should be updated to "main" (although automatic redirect is currently working okay).

I noticed this because despite releasing 0.19.2 today, the link there still showed only v0.19.0 release notes. I should have just made the release note PRs to main and then backported them to v0.19.x so this could not occur. However, shouldn't the "stable" release notes link point to the file in the v0.19.x branch instead?

release_notes_link

Dominant language
HTML
Stars
1
Forks
5
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.