Close the changelog for 0.1.0 - #38
Merged
Merged
Conversation
Step one of the two-step release. Everything that was under [Unreleased] becomes the 0.1.0 section, dated, with an empty [Unreleased] opened above it; the release workflow refuses a tag whose section does not exist, and does so before it builds. Two things fixed on the way, because this section becomes the release notes and both would have shipped inside them: [Unreleased] carried two separate "### Added" headings, so the same category appeared twice in one release. The stray entry - the Settings page naming the signed-in Spotify account - moves into the first block, and loses its note about existing installs needing to sign in again, which cannot apply to a first release. CLAUDE.md still said Offstream requests exactly one scope. It requests two: GET /me needs user-read-private, and that is what puts the account name on the Settings page. The code and SpotifyAuthOptionsTests have said so since that feature landed; the rules file had not caught up, which is the worst place for a stale claim about the app's permission footprint. README stops saying there is nothing to download, and stops telling people they need ffmpeg when a release brings its own.
Uh oh!
There was an error while loading. Please reload this 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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Step one of the two-step release.
## [Unreleased]becomes## [0.1.0] - 2026-08-15with a fresh empty[Unreleased]above it. The release workflow refuses a tag whose section does not exist, and checks before it builds — so this has to merge beforev0.1.0is pushed.Fixed on the way
This section becomes the release notes, so two blemishes in it would have shipped inside them.
Two
### Addedheadings in one release. The stray one held a single entry — the Settings page naming the signed-in Spotify account — which moves into the first block. It also loses its sentence about existing installs needing to sign in again before the account shows: there are no existing installs at 0.1.0.CLAUDE.mdclaimed one scope; the app requests two.GET /meneedsuser-read-private, and that is what puts the account name on the Settings page.SpotifyAuthOptions.DefaultScopesandSpotifyAuthOptionsTestshave both said so since that feature landed — the binding rules file had not caught up, which is the worst possible place for a stale claim about the app's permission footprint. The corrected text also records whyuser-read-emailstays out: Spotify removed theemailfield in its late-2024 cull, so the permission now covers data the endpoint no longer returns.README.mdstops saying there is nothing to download, and stops listing ffmpeg as a prerequisite for people who install a release that bundles it. It gains the SmartScreen warning, since the build is unsigned by design.Verified
Ran the workflow's own two steps against the edited file: the changelog check finds
## [0.1.0], and the notes regex extracts the section cleanly — 52 KB, ending at the last### Securityentry, well inside GitHub's 125 KB release-body limit.No code changed.