fix: republish bias-testing API on @euconform/core as 1.4.0#12
Merged
Conversation
The Apr 15 release bumped core 1.2.0 -> 1.3.0, but @euconform/core@1.3.0 had already been published on Apr 10 from the ECEF release. As a result, the bias-testing additions (./datasets export, CapabilityCache, loadCrowsPairsDataset, sideEffects flag) never made it to npm. Adds a fresh changeset bumping core to 1.4.0 (and dependents to patch) and removes the duplicate 1.3.0 entry that was prepended to the core changelog by the previous release run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…AUDE.md context file
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
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.
Problem
The Apr 15 release (
760d327 chore: release) bumped@euconform/corefrom1.2.0to1.3.0— but@euconform/core@1.3.0had already been published on Apr 10 from the ECEF release. As a result:./datasetsexport,CapabilityCache,loadCrowsPairsDataset,sideEffects: false) never made it to npm.npm view @euconform/core@1.3.0 exportsdoes not list./datasets.packages/core/CHANGELOG.mdended up with a duplicate## 1.3.0header where the bias-testing entry was prepended above the existing ECEF section.Root cause: a manual rollback of
core/package.jsonfrom1.3.0→1.2.0caused Changesets to recompute1.2.0 + minor = 1.3.0, colliding with the existing tag.Fix
@euconform/coreas minor →1.4.0with the bias-testing API.@euconform/cli→1.1.1,@euconform/web→1.2.3(viaupdateInternalDependencies: "patch").## 1.3.0block frompackages/core/CHANGELOG.md. The bias-testing description is regenerated under the new## 1.4.0section when the changeset bot runs.pnpm exec changeset status --verboseconfirms:Test plan
pnpm lint— clean (277 files)pnpm check-types— 9/9 tasks passpnpm test— 262 tests pass (70 web + 164 core + 28 cli)pnpm build— 7/7 packages succeed@euconform/core@1.4.0and@euconform/cli@1.1.1to npm.🤖 Generated with Claude Code