CHANGELOG 6.5.0 entry is missing its link target and an Added heading

未關閉
#253 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

@MatheoPaiva 已經在處理了。

開始於 2026年11月15日。

  • #257 來自 @MatheoPaiva —— 未關閉

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
20/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
停滯
領域
documentation

研究方向

The 6.5.0 heading and entry are at CHANGELOG.md lines 2-3, and the link list at the end of the file holds [Unreleased] near line 250. Compare the 6.5.0 section with the 6.4.0 section, then check open pull request 257 before editing, since it already targets this issue. Done means the section has an Added heading, the trailing space is gone, a [6.5.0]: link exists, and [Unreleased] compares from v6.5.0.

由索引模型根據 Issue 內容生成。

描述

What happens

The 6.5.0 heading has no matching link reference in the list at the bottom of the file, and the [Unreleased] link still compares from v6.4.0. The entry also has no ### Added heading, unlike the other releases, and the line has a trailing space.

Where

CHANGELOG.md:2-3 (heading and entry) and the link list at the end of the file ([Unreleased] at line 250 and the [6.4.0] entry after it).

Why it matters

Impact: Docs and messages (changelog formatting), loud. Severity: Low, because it is a documentation inconsistency only and following the file harms nothing.

How to check

Found by reading the file, not reproduced. Compare the 6.5.0 section with 6.4.0 and look for [6.5.0]: in the link list; the unreleased compare link would become v6.5.0...HEAD.

Version

Seen at v6.5.0. Present on the default branch: present.

主要語言
Java
星號
103
分支
23
平均合併
5 天 8 小時
30 天內合併 PR
3

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Backblaze/b2-sdk-java 的其他 Issue

查看 Backblaze/b2-sdk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。