Skip to content

chore: release packages#12

Merged
clfhhc merged 1 commit into
mainfrom
changeset-release/main
May 26, 2026
Merged

chore: release packages#12
clfhhc merged 1 commit into
mainfrom
changeset-release/main

Conversation

@graphrefly-write-content

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@graphrefly/graphrefly@0.49.0

Minor Changes

@graphrefly/pure-ts@0.49.0

Minor Changes

@graphrefly/rn-hermes-fixture@0.0.7

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/pure-ts@0.49.0

@graphrefly-examples/basic-state-and-derived@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/compat-jotai@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/compat-nanostores@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/compat-zustand@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/framework-react@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/framework-solid@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/framework-svelte@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/framework-vue@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/harness-refine-hello@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/inbox-reducer@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/knowledge-graph@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/nestjs-order-flow@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/reactive-layout-flow@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly-examples/spending-alerts@0.0.8

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@graphrefly/cli@0.0.9

Patch Changes

  • Updated dependencies [4230039]:
    • @graphrefly/graphrefly@0.49.0

@clfhhc clfhhc merged commit 7d2893b into main May 26, 2026
1 check passed
@clfhhc clfhhc deleted the changeset-release/main branch May 26, 2026 04:53
clfhhc added a commit that referenced this pull request May 27, 2026
…uard anti-pattern #12

Companion to graphrefly-rs `ff12b4b` (the actual /qa fix slice). This
commit covers the TS-side fallout:

# Stale commit hashes refreshed (G2.1, Blind #16/#17)

graphrefly-rs commits got rebased on top of `dda5dab chore: release
v0.0.9` between the original landing and this /qa pass. Pre-rebase
hashes `6fadc5d` / `7d2721d` / `1f7c5c7` were referenced in:

- `docs/rust-port-decisions.md` — D298/D299/D300/D301 entries (7 hash
  references across 5 lines).
- `docs/cross-track-ledger.md` — §1 D298 row + §1 D301 row.

Post-rebase canonical hashes are:
- `6fadc5d` → `e9d1e7a` (D298 substrate)
- `7d2721d` → `a89e519` (D300 + D299 closure)
- `1f7c5c7` → `9267779` (D301)

Future audit scripts that walk the decision log to find landing
commits would have dereferenced dangling orphans (or post-GC, no
match at all). Refresh prevents provenance loss.

# Decision-guard anti-pattern #12 (D301 lesson)

Added to `.claude/skills/decision-guard/SKILL.md`'s "Recurring
anti-patterns to call out" section. The D301 B.a/B.b sub-decisions
were framed as orthogonal during the Q4 sub-decision lock — they
weren't. B.a let users register `_anon_42`; B.b emitted `_anon_42`
for unresolvable cross-mount deps with NodeId(42). The
`SnapshotError::UnresolvableDeps` diagnostic became ambiguous —
collision caught only at /qa, not at design lock.

**Lesson pinned:** when sub-decisions are framed as orthogonal,
sketch one input that exercises BOTH simultaneously — confirm the
orthogonality survives the example before locking. The B.a/B.b case
took ~30s: "user registers a node named `_anon_42`; snapshot encodes
an unresolvable dep with NodeId(42); what does the diagnostic say?"
Had that sketch been part of the lock checklist, the coupling would
have surfaced at design-time. Anti-pattern #12 makes this a mandatory
pre-lock micro-check for any multi-sub-decision question.

Source: D301 /qa (2026-05-26). Resolved at the substrate level by
changing the snapshot marker format to `_anon::<rawid>` (the `::`
is structurally rejected by `validate_name` as `PATH_SEP`); see
graphrefly-rs commit `ff12b4b` for the substrate fix.

# Not in this commit

`docs/optimizations.md` + `archive/docs/SESSION-handle-dispatch-
substrate.md` are user work-in-progress for a separate design
thread (Handle-Dispatch Substrate). Left uncommitted for the user
to land separately.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

1 participant