Conversation
There was a problem hiding this comment.
Pull request overview
Release automation PR for @btravstack/entity that prepares the repository metadata for publishing version 0.7.1 to npm (per Changesets), reflecting a documentation-only patch associated with issue #60.
Changes:
- Bump
@btravstack/entityversion to0.7.1. - Add
0.7.1release notes to the package changelog. - Remove the consumed changeset file now that it has been released.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/entity/package.json | Updates the package version to 0.7.1 for publication. |
| packages/entity/CHANGELOG.md | Adds the 0.7.1 patch entry describing the documentation-only change. |
| .changeset/computed-self-reference-annotation.md | Removes the changeset after it has been applied to the release. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
084e1df to
6ac4a27
Compare
6746d53 to
12be092
Compare
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configurationConfiguration used: Repository: btravstack/entity/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe package version changed from 0.7.0 to 0.8.0. The changelog documents deep-strict equality behavior, the Node-only runtime requirement, and self-referencing ChangesEntity package release
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This release updates package metadata and changelog entries without introducing a new runtime restriction. No actionable merge-blocking risk remains beyond normal release checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
d883bb9 to
f022682
Compare
fa4c8f9 to
7153633
Compare
e607641 to
8df35db
Compare
8df35db to
73ed9d1
Compare
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
@btravstack/entity@0.8.0
Minor Changes
c02be10:
equalsnow delegates tonode:util'sisDeepStrictEqualinstead of ahand-rolled traversal. Behaviour is unchanged for every case the suite pins —
bigint,Set/Mapby contents, nested key order, typed arrays andArrayBufferbytewise,RegExp,Date, and cyclic values — with onedifference:
+0and-0now compare unequal (Object.issemantics) wherethe previous implementation treated them as equal (SameValueZero).
This makes the package Node-only: it now imports a
node:builtin, so abrowser or edge bundle without a
node:utilshim will fail to resolve it.Patch Changes
02c29e3: Document the self-referencing deriver idiom (computed derivers cannot reference the entity's own statics (TS2506) #60): a
computedderiver or anEntity.invariantpredicate may call the entity's own statics, given anexplicit return annotation —
(d): boolean => Doc.isActive(d.tags). Theunannotated form is
TS2506, which is TypeScript resolving the deriver'sinferred return type inside the class's own base expression, not a rule of
the library. The annotation is still checked against both the body and the
schema.
computed.test-d.tspins the idiom, the wrong-annotation errors, andthe
this-parameter dead end (TS2502).Documentation only; no runtime or API change.