chore: back-merge v0.1.13 into develop#108
Merged
Merged
Conversation
Cuts release/v0.1.13 from develop. Highlights: - shared/ui catalogue + /playground showcase (PRD-018, RFC-016) - rule 24 — shared/ui ownership and customisation discipline - new primitive variants from rule-24 audit (ghost-mono, mono, outline-mono, banner) - orch theme (Orchestra-inspired) as 5-click easter egg + 2s freeze - dense-graph render-resilience for Sankey + Tree - adoption of svelte-sonner Toaster - reverted Force 3D experimental Threlte view (#103/#104/#105) Refs: PRD-018, RFC-016, EVID-022, EVID-023, EVID-024, PRD-019
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
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.
Summary
Back-merge of v0.1.13 release artifacts into
developperguides/GIT-FLOW-GUIDE.ru.md§2.5 step 10.Brings the version bump (
0.1.12 → 0.1.13) and the v0.1.13 CHANGELOG entry intodevelop.Why
Release was cut from
release/v0.1.13and merged tomainvia #107, then taggedv0.1.13and published to npm viarelease.yml. Without this back-merge:developstays onpackage.json#version: 0.1.12while npm has0.1.13maindevelopwould re-introduce the version bump as a conflict at next releaseThe
release/v0.1.13branch was deleted from origin after merge tomain, so this PR is opened from a freshchore/back-merge-v0.1.13branch built off the same bump commit (8677321).Test plan
develop--merge(preserve commit in history)🤖 Generated with Claude Code