Fix release workflow: remove invalid xpecs bump from changeset#10
Merged
Conversation
The root "xpecs" package.json isn't listed in the npm workspaces field (only packages/*, skill, website are), so changesets doesn't recognize it as a workspace package. The modern-icon-library changeset referenced "xpecs": minor, which made `changeset version` fail in CI with "Found changeset modern-icon-library for package xpecs which is not in the workspace".
The `@xpecs` scope is unavailable on npm, so this renames it across all workspace packages (`@prescriptive/tokens`, `@prescriptive/xote`, `@prescriptive/reativa`, `@prescriptive/skill`), the lockfile, changesets, docs, build scripts, and the website's ReScript/Reativa sources. The root private package (name "xpecs") and the website package (name "xpecs-website") are unscoped and unaffected.
brnrdog
force-pushed
the
claude/changeset-release-workflow-error-1lyx99
branch
from
July 23, 2026 20:58
c13a39b to
45feafc
Compare
Rebrands the project throughout: the display name (Xpecs -> Prescriptive) in docs, website UI, and the Agent Skill; the root package (`xpecs` -> `prescriptive`) and the website package (`xpecs-website` -> `prescriptive-website`); internal DOM id prefixes (`xpecs-*` -> `prescriptive-*`) in the Xote and Reativa component sources; the `prescriptive_reativa` build directory; and the repository URLs and schema `$id`s (github.com/brnrdog/ux-archetypes -> github.com/brnrdog/prescriptive), plus the project-name npm keyword. The GitHub Pages base path is derived from the repo name at deploy time, so it follows the repository rename automatically. Historical CHANGELOG entries are left intact, since they record the name the project actually had at the time.
`Switch` and `Checkbox` both declare a `~label` string argument and
rendered their wrapper with the mlx `<label>` host element. The mlx JSX
desugars `<label>` to the `label` binding from `Reativa.View.Mlx`, but
the `~label` argument shadows it, so the compiler saw a `string` where a
host-element constructor was expected:
Error: This expression has type string
This is not a function; it cannot be applied.
Build the wrapper with `View.element ... "label"` instead — the same
approach `Field.mlx` already uses to avoid this exact collision. The
inner `<span>` elements are unaffected (no shadowing) and stay as JSX.
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
2 participants
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.
The root "xpecs" package.json isn't listed in the npm workspaces field (only packages/*, skill, website are), so changesets doesn't recognize it as a workspace package. The modern-icon-library changeset referenced "xpecs": minor, which made
changeset versionfail in CI with "Found changeset modern-icon-library for package xpecs which is not in the workspace".