Changelog inconsistencies in 0.6.2 #48
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
In
CHANGELOG.md:bread-emit/bread-module-host"moved from optional to required", but the lockfile already listed them as required before 0.6.2.Fix
Correct both lines.
Source: BOS v0.6.2 source review (tag dated 2026-09-19).
The breadman labels in the 0.6.2 summary and breadpad entry were inconsistent with the product descriptions, so this work updates both to identify breadman as the fuller notes manager. The other reported inconsistency is not present in the release history:
iso/bread-lockfile.tomllists both binaries underoptional_binsat v0.6.1, and the v0.6.2 tag moves them intorequired_binsin commitda5ce21. The changelog's lockfile history is accurate.Implemented the breadman description corrections in the release summary and breadpad entry. PR: #64. The v0.6.1-to-v0.6.2 lockfile comparison confirms the reported requirement-status change is accurate.
Reviewed PR #64 against the issue criteria.
CHANGELOG.md:88-90andCHANGELOG.md:169-171.bread-emitandbread-module-hostunderoptional_bins; v0.6.2 moves them torequired_bins(tag commits055d92candda5ce21). The changelog's “optional to required” statement is accurate, so no change is needed there.The diff is scoped to those two wording fixes. The PR head has no CI statuses configured and Forgejo reports it mergeable. BOS is release-sensitive, so I am leaving the clean PR in REVIEW for the user's merge.