Repository navigation
chore(release): version packages - #34
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
October 15, 2026 14:51
d29b907 to
1268b17
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
October 15, 2026 14:52
1268b17 to
856d09a
Compare
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 master, this PR will be updated.
Releases
@unclecat/mcp-multi-db@1.0.0
Major Changes
a1c7781Thanks @unclecatvn! - 1.0.0 marks the stable API. Nothing changes for you since 0.0.8: same tools, arguments, config file and env vars. From now on releases follow semver strictly, so a removed or renamed tool, argument, error code or env var, or a changed default, only ships in a new major. Install withnpx -y @unclecat/mcp-multi-db@1to get every 1.x fix and feature without breaking changes.@unclecat/mcp-obsidian@1.0.0
Major Changes
a1c7781Thanks @unclecatvn! - 1.0.0 marks the stable API. Nothing changes for you since 0.0.2: same tools, arguments and env vars. From now on releases follow semver strictly, so a removed or renamed tool, argument, error code or env var, or a changed default, only ships in a new major. Install withnpx -y @unclecat/mcp-obsidian@1(instead of@latest) to get every 1.x fix and feature without breaking changes.@unclecat/mcp-odoo@1.0.0
Major Changes
0b9d8daThanks @unclecatvn! - Breaking:ODOO_INPUT_INVALIDis gone (validation errors now readInput validation error: ...) andsearch_readdefaults tolimit: 100.name_searchwith adomainon Odoo 19 (unexpected keyword argument 'args'): name and domain are now sent positionally, which works on 18 and 19.ODOO_TRANSPORT_FAILEDinstead of hanging.search_readdefaults tolimit: 100and returnslimit_reached: truewhen a page is full.readOnlyHinton reads,destructiveHintonwrite/unlink/call_method).McpServer.registerToolwith zod schemas (single source of truth); unknown arguments are still rejected. Validation failures now readInput validation error: ...instead of[ODOO_INPUT_INVALID].index.d.ts(it declared exportsindex.jsnever had).Minor Changes
d320447Thanks @unclecatvn! - Odoo 19+ support without the deprecated APIs:POST /json/2/<model>/<method>, bearer auth) instead of/jsonrpc, which Odoo 19 deprecates (removal planned for Odoo 22) and logs a warning for on every call. Odoo 18 and password auth keep using/jsonrpc.read_groupon Odoo 19+ callsformatted_read_groupinstead of the deprecatedread_group, and reshapes the result to the same output shape (differences are listed in the README).GET /web/versionand shown asserverVersioninlist_connections.