Release 0.19.1#208
Merged
Merged
Conversation
7feacd4 to
029fc81
Compare
029fc81 to
2969ae9
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #208 +/- ##
==========================================
+ Coverage 88.86% 88.94% +0.08%
==========================================
Files 72 72
Lines 3610 3610
Branches 585 585
==========================================
+ Hits 3208 3211 +3
+ Misses 219 217 -2
+ Partials 183 182 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
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
@elek-io/core@0.19.1
Patch Changes
b02e71a: Ship the consumer documentation inside the published package
The package now includes its consumer documentation under
docs/, available offline and matched to the installed version atnode_modules/@elek-io/core/docs/with no network lookup. This lets developers and AI coding agents work from accurate, version-matched references. Start atdocs/index.md, and see the README's "Using Core with AI agents" section for how to point an agent at them.Documentation is now split by audience. Consumer docs live in
docs/and ship with the package. Contributor and design docs live incontributing/and are not published, so a few docs moved there (testing, language-scoped validation, migration and history flow, how to add a field type, error-handling internals, and the cross-CMS comparison).76ab883: Fix Asset binary loss when replacing a file with one of the same extension
Replacing an Asset's file through
updatewith anewFilePathof the same extension deleted the binary it had just written, because the previous and new paths inlfs/were identical. The previous binary is now removed only when the extension actually changes. Listing and counting Assets also enumerate the JSON metadata inassets/instead of thelfs/binaries, so an Asset whose binary is missing or not yet fetched stays listed and recoverable rather than disappearing.1ffe2d2: Update dependencies to their latest versions
All runtime and development dependencies are updated to their latest published versions and pinned to exact versions.
@types/nodestays on the Node 24 LTS line (24.13.2) to match the supported runtime rather than moving to a non-LTS release. Thedugitepeer dependency moves to 3.2.2.