chore(release): 1.0.8 — release the unreleased isCompatible fix - #7
Open
kriszyp wants to merge 1 commit into
Open
chore(release): 1.0.8 — release the unreleased isCompatible fix#7kriszyp wants to merge 1 commit into
kriszyp wants to merge 1 commit into
Conversation
Releases the isCompatible forwarding fix (#6, merged 2026-07-02), which has been sitting unreleased on main for five weeks. harper pins structon ^1.0.7 and 1.0.7 is the last published version, so the fix cannot reach any Harper build until this is cut. harper#1441 tracks the resulting silent structure clobber and names a 5.1.6 stage cluster incident. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
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.
Version bump only. One line.
Why this is needed
structon's last npm publish is 1.0.7 (2026-06-10). PR #6 — fix: forwardisCompatiblefrom_saveTypedStructurestosaveStructures— merged 2026-07-02 and is the only commit onmainsince that tag.package.jsononmainstill reads1.0.7, so it was never version-bumped and never published.harper pins
"structon": "^1.0.7". Because 1.0.7 is the newest published version, that range resolves to 1.0.7 in every Harper build — so the fix has been unreachable for five weeks despite being merged.What it unblocks
HarperFast/harper#1441, where the missing
isCompatibleforwarding causes a silent typed-structure clobber. That issue names a 5.1.6 stage-cluster incident, and it is currently P1 for exactly this reason: the fix exists, it just isn't in a release anyone can install.After this merges
Publish 1.0.8 to npm, then bump harper's pin to
^1.0.8so the resolution is explicit rather than relying on the caret picking up a newly published version at some future install time.Found while triaging the harper backlog — flagging rather than assuming, since cutting a release is a call for a human.
🤖 Generated with Claude Code