Repository navigation
chore(release): publish app-kit 34.0.0 - #492
Merged
Merged
Conversation
…-develop-33.3.0 chore: back-merge main (33.3.0) into develop
…e-counts feat(genre-tree): distinguish catalogue and playlist selections
There was a problem hiding this comment.
Copilot was unable to review this pull request due to rate limiting. Please try again later. See Usage limits for GitHub Copilot for details.
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Release app-kit and app-kit-ui 34.0.0 together. Reference genre panels distinguish the playable catalogue from actual playlist membership and preserve explicit canonical/regional/all selections through playback.
Changes
me) responses remain compatible.Compatibility and recovery
Major version required by the strict reference parser contract. Grow API PR415 is merged and delivers it. Grow frontend PR507 is draft until this release is published and pinned. Hear is outside this rollout and retains its existing dependency; shared personal behavior remains supported. No data migration or production deployment. Consumers can retain/revert to 33.3.0 if migration is deferred; published versions/tags must never be moved.
Release contract
Strict Gitflow: release/34.0.0 from develop04c7386 into main1cb34c7 (previous v33.3.0 dereferences to that main SHA). CI owns annotated v34.0.0 and the existing publisher owns both npm packages followed by the GitHub Release. Verify the exact merged/tag commit and both artifacts, then back-merge released main into develop. No manual tag or direct npm publication.
Test plan