Skip to content

docs: backdated and new release notes#1181

Open
hieblmi wants to merge 1 commit into
lightninglabs:masterfrom
hieblmi:release-notes
Open

docs: backdated and new release notes#1181
hieblmi wants to merge 1 commit into
lightninglabs:masterfrom
hieblmi:release-notes

Conversation

@hieblmi

@hieblmi hieblmi commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

This PR adds a docs/release-notes folder and adds backdated release notes.

@gemini-code-assist

Copy link
Copy Markdown

Caution

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

@hieblmi
hieblmi requested a review from starius July 21, 2026 20:19
@hieblmi
hieblmi force-pushed the release-notes branch 3 times, most recently from b7e78e7 to 63e4227 Compare July 22, 2026 08:21
@hieblmi hieblmi self-assigned this Jul 22, 2026
Comment thread .github/pull_request_template.md Outdated
@@ -1,2 +1,3 @@
#### Pull Request Checklist
- [ ] Update `release_notes.md` if your PR contains major features, breaking changes or bugfixes
- [ ] Update `docs/release-notes/release-notes-template.md` if your PR contains

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be not the template here. We need another growing file for a future release. Like docs/release-notes/release-notes-next.md

@hieblmi
hieblmi requested a review from starius July 23, 2026 21:10
@starius

starius commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Missing releases: v0.1.3-beta, v0.2.0-alpha, v0.6.1-beta, v0.15.1-beta, v0.25.0-beta, v0.25.1-beta, v0.26.1-beta, v0.31.3-beta, v0.31.5-beta-lnd0.20, and v0.31.6-beta.

Consequently, previous/next navigation also skips real tags, for example v0.6.0-beta jumps directly to v0.6.2-beta, and there some issues with particular releases:

v0.34.0-beta is already released, but it is accounted as "Unreleased".

The v0.1.1 build block extracts loop-source-v0.1-alpha and embeds Commit=v0.1-alpha. The v0.2 similarly asks for v0.1-alpha manifests/source and builds with the old tag. These errors existed in the historical prose, but reproducing them makes the new archive factually unsafe; they should be corrected or omitted while retaining the historical release ideas.

Document every published Loop release and preserve authoritative notes.

Add the next-release workflow and rebuild chronological navigation.

Rename the reproducible-build guide for clarity.
@hieblmi

hieblmi commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks for the detailed review @starius, I've addressed all issues you found!

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