Version Packages#26
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
fa147aa to
cb10d60
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
cb10d60 to
9171e9e
Compare
Update yarn.lock after Changesets versioning and remove Linux-only cache artifacts generated by the release action so immutable install passes locally. Related: #21 Generated-by: Codex/GPT-5.4
Owner
|
Release prep verification update:
Note: |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
@mandel59/mojidata-api@2.0.0
Major Changes
c121956Thanks @mandel59! - Move the native Node.js backends out of the portablemojidata-apiruntime andcompatibility facade.
@mandel59/mojidata-apiand@mandel59/mojidata-api-runtimenow keep thedefault
sql.jspath only, while the native backends are published as the newexplicit packages
@mandel59/mojidata-api-better-sqlite3and@mandel59/mojidata-api-node-sqlite.Minor Changes
d75402fThanks @mandel59! - Add/api/v1/idsfindproperty existence filters with.hasand.notHas, and add dictionary/index-like Unihan property value search keys such asunihan.kMorohashiandunihan.kMorohashi.glob.#39
9e5fa3aThanks @mandel59! - Add documented bundler-safe mojidata-api entrypoints, public runtime/sqlite-wasmsubpath exports, static entrypoint smoke tests, and sqlite-wasm idsfind FTS5
schema validation.
Patch Changes
#38
6c932e6Thanks @mandel59! - Add a generatedunihan_value_refreverse lookup table and use it forunihan_ftsqueries so D1-backed/api/v1/mojidatarequests no longer scan thefull Unihan value table.
#38
ce35942Thanks @mandel59! - AddCache-Control: no-storeto mojidata-api JSON responses so D1 blue/greencutovers are not hidden by stale consumer-side caches.
Updated dependencies [
efd9a85,6c932e6,d75402f,c121956,ce35942,30b6de0,9e5fa3a]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-api-runtime@2.0.0
Major Changes
c121956Thanks @mandel59! - Move the native Node.js backends out of the portablemojidata-apiruntime andcompatibility facade.
@mandel59/mojidata-apiand@mandel59/mojidata-api-runtimenow keep thedefault
sql.jspath only, while the native backends are published as the newexplicit packages
@mandel59/mojidata-api-better-sqlite3and@mandel59/mojidata-api-node-sqlite.Minor Changes
9e5fa3aThanks @mandel59! - Add documented bundler-safe mojidata-api entrypoints, public runtime/sqlite-wasmsubpath exports, static entrypoint smoke tests, and sqlite-wasm idsfind FTS5
schema validation.
Patch Changes
30b6de0Thanks @mandel59! - Add the initial SQLite wasm OPFS backend package formojidata-api, includingan OO1
SqlExecutoradapter, OPFS SAH pool materialization helpers, and abrowser worker entrypoint.
6c932e6,d75402f]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/idsdb-fts5@1.9.0
Minor Changes
efd9a85Thanks @mandel59! - Publish the neutral@mandel59/idsdb-fts5package and make thebetter-sqlite3andnode:sqlitemojidata-api backends prefer the FTS5idsfind.dbbuild by default.All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata@1.8.0
Minor Changes
6c932e6Thanks @mandel59! - Add a generatedunihan_value_refreverse lookup table and use it forunihan_ftsqueries so D1-backed/api/v1/mojidatarequests no longer scan thefull Unihan value table.
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-api-better-sqlite3@1.9.0
Minor Changes
efd9a85Thanks @mandel59! - Publish the neutral@mandel59/idsdb-fts5package and make thebetter-sqlite3andnode:sqlitemojidata-api backends prefer the FTS5idsfind.dbbuild by default.c121956Thanks @mandel59! - Move the native Node.js backends out of the portablemojidata-apiruntime andcompatibility facade.
@mandel59/mojidata-apiand@mandel59/mojidata-api-runtimenow keep thedefault
sql.jspath only, while the native backends are published as the newexplicit packages
@mandel59/mojidata-api-better-sqlite3and@mandel59/mojidata-api-node-sqlite.Patch Changes
efd9a85,6c932e6,d75402f,ce35942]:@mandel59/mojidata-api-core@1.9.0
Minor Changes
d75402fThanks @mandel59! - Add/api/v1/idsfindproperty existence filters with.hasand.notHas, and add dictionary/index-like Unihan property value search keys such asunihan.kMorohashiandunihan.kMorohashi.glob.Patch Changes
6c932e6Thanks @mandel59! - Add a generatedunihan_value_refreverse lookup table and use it forunihan_ftsqueries so D1-backed/api/v1/mojidatarequests no longer scan thefull Unihan value table.
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-api-d1@1.9.0
Minor Changes
bde6aafThanks @mandel59! - Add env-based app and fetch handler helpers for embedding the D1 backend inCloudflare Worker applications.
Patch Changes
6c932e6,d75402f,ce35942]:@mandel59/mojidata-api-node-sqlite@1.9.0
Minor Changes
efd9a85Thanks @mandel59! - Publish the neutral@mandel59/idsdb-fts5package and make thebetter-sqlite3andnode:sqlitemojidata-api backends prefer the FTS5idsfind.dbbuild by default.c121956Thanks @mandel59! - Move the native Node.js backends out of the portablemojidata-apiruntime andcompatibility facade.
@mandel59/mojidata-apiand@mandel59/mojidata-api-runtimenow keep thedefault
sql.jspath only, while the native backends are published as the newexplicit packages
@mandel59/mojidata-api-better-sqlite3and@mandel59/mojidata-api-node-sqlite.Patch Changes
efd9a85,6c932e6,d75402f,ce35942]:@mandel59/mojidata-api-sqlite-wasm@1.9.0
Minor Changes
#24
30b6de0Thanks @mandel59! - Add the initial SQLite wasm OPFS backend package formojidata-api, includingan OO1
SqlExecutoradapter, OPFS SAH pool materialization helpers, and abrowser worker entrypoint.
#39
9e5fa3aThanks @mandel59! - Add documented bundler-safe mojidata-api entrypoints, public runtime/sqlite-wasmsubpath exports, static entrypoint smoke tests, and sqlite-wasm idsfind FTS5
schema validation.
Patch Changes
6c932e6,d75402f,c121956,30b6de0,9e5fa3a]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-api-hono@1.8.1
Patch Changes
ce35942Thanks @mandel59! - AddCache-Control: no-storeto mojidata-api JSON responses so D1 blue/greencutovers are not hidden by stale consumer-side caches.
6c932e6,d75402f]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-api-sqljs@1.8.1
Patch Changes
6c932e6,d75402f,c121956,ce35942,30b6de0,9e5fa3a]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/mojidata-cli@1.7.1
Patch Changes
6c932e6Thanks @mandel59! - Add a generatedunihan_value_refreverse lookup table and use it forunihan_ftsqueries so D1-backed/api/v1/mojidatarequests no longer scan thefull Unihan value table.
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
@mandel59/react-mojidata-api@1.7.1
Patch Changes
6c932e6,d75402f,c121956,ce35942,30b6de0,9e5fa3a]:All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.