deps: bump BareDOM 2.9.0 → 3.0.0#56
Merged
Merged
Conversation
The major version reflects internal API additions in BareDOM (dispatch
hooks, state-mutation hooks, lifecycle hooks, component-id tracking)
introduced to wire the new x-trace-history debugger dock, plus an
x-select bugfix ("don't stomp slotted <option selected> default",
PR #127). Public consumer surface is unchanged; Bareforge compiles
clean and all four PR-readiness gates pass against 3.0.0.
No new consumer components — x-trace-history is the only new export,
and it is explicitly a dev-only debugger dock (its own ns docstring:
"the dock is not a consumer-facing component, has no model.cljs
under components/, contributes nothing to custom-elements.json").
It self-activates on import and only renders when the URL flag
?baredom-trace-history is present. Nothing for Bareforge's palette
or inspector to scaffold.
Lockstep with src/bareforge/meta/versions.cljs preserved per CLAUDE.md
and enforced by test/bareforge/meta/versions_test.cljs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Routine consumer-side bump. BareDOM's 3.0.0 release is the addition of the x-trace-history debugger dock and its supporting internal hooks (dispatch / state-mutation / lifecycle / component-id tracking); the major version reflects internal-API additions, not a public-surface break. Bareforge compiles clean — all four PR-readiness gates pass against 3.0.0.
No scaffolding needed
`x-trace-history` is not a consumer component — quoting its own namespace docstring:
It self-activates on import and only renders when the URL flag `?baredom-trace-history` is present. Nothing for Bareforge's palette or inspector to onboard.
Lockstep
Both edits made in the same commit as required by CLAUDE.md (and enforced by `test/bareforge/meta/versions_test.cljs`):
Notable BareDOM bugfix worth manual smoke
PR #127 in BareDOM 3.0.0: "fix(x-select): don't stomp slotted
<option selected>default". Bareforge PR #55 (recently merged) routed every inspector x-select through a host-`value` mirror because the `` path wasn't being honoured. The new BareDOM behaviour is orthogonal to our fix, but the inspector enum pickers (placement, variant, size, type) are worth a quick eyeball.Test plan
🤖 Generated with Claude Code