developer-tools Static interface comparison
CloudBase
2.37.5 2.37.6
No policy-significant interface change detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 3Modified tools
- 0Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
3 tools with recorded changes
deployApplyModifiedWhat changed
- deployApply: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- Previous解析 cloudbaserc 并按 database→functions→app→hosting→gateway 顺序执行声明式部署。这是 deployPlan 的执行对仗工具(plan 预演 / deployApply 执行同一份 cloudbaserc),属于本地形态的 apply(读本地 cloudbaserc 并在本地构建上传),是会变更云端资源的写操作,必须显式传 confirm=true 才会执行。建议先用 deployPlan 预演,确认计划无误后再执行。 适用边界:本工具用于项目级声明式编排(一份 cloudbaserc 统一 plan/apply);单资源临时直传请用 manageFunctions/manageHosting/manageApps。 - confirm:必须显式传 true 才执行部署,否则直接拒绝 - confirmDestructive:当本次待执行的数据库迁移含破坏性语句(DROP/TRUNCATE/DELETE、ALTER…DROP/RENAME)时,除 confirm 外还必须显式传 confirmDestructive=true 才会执行;否则拒绝并列出命中的迁移与语句。无破坏性迁移时该参数不生效 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置 - envId:目标环境 ID,优先级高于 cloudbaserc 中的 envId;不传则用配置值或当前绑定环境 - only:仅部署指定资源类型 - skip:跳过指定资源类型 - yes:遇到已存在资源时的处理方式。true=直接覆盖更新;false(默认)=保守跳过,在无法交互确认的场景下已存在资源不会被覆盖(与 deployPlan 的 yes 语义一致) - concurrency:同类型资源最大并行数,默认 1(串行) - continueOnError:某个资源失败后继续部署其余资源(database 失败仍强制中断)
- Current解析 cloudbaserc 并按 database→functions→app→hosting→gateway 顺序执行声明式部署。这是 deployPlan 的执行对仗工具(plan 预演 / deployApply 执行同一份 cloudbaserc),属于本地形态的 apply(读本地 cloudbaserc 并把本地产物上传到云端),是会变更云端资源的写操作,必须显式传 confirm=true 才会执行。建议先用 deployPlan 预演,确认计划无误后再执行。 ⚠️ 只部署不构建:本工具不会执行任何构建命令(app 与 hosting 都不会)。cloudbaserc 里的 buildCommand / installCommand / framework 只用于推断产物目录,不会被执行。产物目录不存在或为空时报 BUILD_OUTPUT_NOT_FOUND —— hosting 先调 deployBuild,app 需让用户在项目目录执行其构建命令,完成后重试,不要改配置绕过。构建前可用 deployPlan 读取 buildHint.buildCommand / outputDir / artifactReady 确认该跑什么。app 需要云端构建时用 CLI `tcb app deploy`(本工具不提供云端构建)。 适用边界:本工具用于项目级声明式编排(一份 cloudbaserc 统一 plan/apply);单资源临时直传请用 manageFunctions/manageHosting/manageApps。 - confirm:必须显式传 true 才执行部署,否则直接拒绝 - confirmDestructive:当本次待执行的数据库迁移含破坏性语句(DROP/TRUNCATE/DELETE、ALTER…DROP/RENAME)时,除 confirm 外还必须显式传 confirmDestructive=true 才会执行;否则拒绝并列出命中的迁移与语句。无破坏性迁移时该参数不生效 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置 - envId:目标环境 ID,优先级高于 cloudbaserc 中的 envId;不传则用配置值或当前绑定环境 - only:仅部署指定资源类型 - skip:跳过指定资源类型 - yes:遇到已存在资源时的处理方式。true=直接覆盖更新;false(默认)=保守跳过,在无法交互确认的场景下已存在资源不会被覆盖(与 deployPlan 的 yes 语义一致) - concurrency:同类型资源最大并行数,默认 1(串行) - continueOnError:某个资源失败后继续部署其余资源(database 失败仍强制中断)
Input schema
Input schema unchanged.
13 unchanged entries
(schema root)concurrencyconfirmconfirmDestructivecontinueOnErrorcwdenvIdmodeonlyonly › [items]skipskip › [items]yes
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
deployBuildModifiedWhat changed
- deployBuild: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- Previous解析 cloudbaserc 并对 hosting[] 中配置了 buildCommand 的项目执行本地构建(仅执行 buildCommand,不安装依赖、不上传)。对应 CLI 的 tcb app build,但只处理 hosting[] 静态托管项,与 cloudbaserc 的 app 资源类型(云端构建管线)无关。声明式 hosting 部署拆分为「build → plan → apply」三步,本工具是第一步:先本地构建产物,再 deployPlan 预演,最后 deployApply 上传产物。deployApply 不再隐式本地构建 —— 带构建命令的 hosting 项在产物缺失时会报错引导先执行本工具。纯静态托管(未配置 buildCommand 且无法探测框架)自动跳过。构建为纯本地操作:不解析环境、不要求登录,也不需要 confirm。 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置
- Current解析 cloudbaserc 并对 hosting[] 中配置了 buildCommand 的项目执行本地构建(仅执行 buildCommand,不安装依赖、不上传)。只处理 hosting[],不处理 cloudbaserc 的 app 资源 —— app 的产物需要你自己在项目目录构建(产物目录与构建命令可从 deployPlan 的 buildHint 读取),或改用 CLI `tcb app deploy` 走云端构建。声明式 hosting 部署拆分为「build → plan → apply」三步,本工具是第一步:先本地构建产物,再 deployPlan 预演,最后 deployApply 上传产物。deployApply 对 app 与 hosting 都不构建 —— 产物缺失时报 BUILD_OUTPUT_NOT_FOUND,hosting 可用本工具补齐,app 需你自行构建。纯静态托管(未配置 buildCommand 且无法探测框架)自动跳过。构建为纯本地操作:不解析环境、不要求登录,也不需要 confirm。 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)cwdmode
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
deployPlanModifiedWhat changed
- deployPlan: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- Previous解析 cloudbaserc 并计算声明式部署计划(dry-run,不产生任何变更)。这是 deployApply 的预演对仗工具:plan 计算、deployApply 执行同一份 cloudbaserc。返回每个资源的动作分类:create=新建,update=覆盖更新,skip=无变更/不会执行,conflict=检测到冲突需中断,deploy=直传覆盖。计划已按 yes 复算为「实际会发生的动作」:不传 yes=true 时,云端已存在的函数会标为 skip(并在 declaredStatus 保留 update),与 deployApply 的实际执行结果一致,避免预演与执行相反。 适用边界:本工具用于项目级声明式编排(一份 cloudbaserc 统一 plan/apply);单资源临时直传请用 manageFunctions/manageHosting/manageApps。 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置 - envId:目标环境 ID,优先级高于 cloudbaserc 中的 envId;不传则用配置值或当前绑定环境 - only:仅计算指定资源类型的计划 - skip:跳过指定资源类型 - yes:与 deployApply 的 yes 对齐,用于复算已存在函数的有效动作。true=预演为覆盖更新(update);false(默认)=预演为保守跳过(skip)
- Current解析 cloudbaserc 并计算声明式部署计划(dry-run,不产生任何变更)。这是 deployApply 的预演对仗工具:plan 计算、deployApply 执行同一份 cloudbaserc。返回每个资源的动作分类:create=新建,update=覆盖更新,skip=无变更/不会执行,conflict=检测到冲突需中断,deploy=直传覆盖。计划已按 yes 复算为「实际会发生的动作」:不传 yes=true 时,云端已存在的函数会标为 skip(并在 declaredStatus 保留 update),与 deployApply 的实际执行结果一致,避免预演与执行相反。 ⚠️ app / hosting 的计划项一律是「直传已有产物」:声明式部署只部署不构建,cloudbaserc 的 buildCommand / framework 只用于推断产物目录,不会被执行。 app / hosting 的计划项带 buildHint = { buildCommand, outputDir, artifactReady }(机器可读,不要去解析 details 里的中文文案):artifactReady=false 表示产物目录缺失或为空,此时 deployApply 必定失败(BUILD_OUTPUT_NOT_FOUND)。正确做法是先构建再 apply —— hosting 可调用 deployBuild;app 需在项目目录执行 buildHint.buildCommand(为 null 则本就无需构建)。构建完成后重新 deployPlan 确认 artifactReady=true,不要改配置绕过。 适用边界:本工具用于项目级声明式编排(一份 cloudbaserc 统一 plan/apply);单资源临时直传请用 manageFunctions/manageHosting/manageApps。 - cwd:项目根目录,默认当前工作目录 - mode:环境名,命中 envOverrides.<mode> 时合并对应的多环境覆盖配置 - envId:目标环境 ID,优先级高于 cloudbaserc 中的 envId;不传则用配置值或当前绑定环境 - only:仅计算指定资源类型的计划 - skip:跳过指定资源类型 - yes:与 deployApply 的 yes 对齐,用于复算已存在函数的有效动作。true=预演为覆盖更新(update);false(默认)=预演为保守跳过(skip)
Input schema
Input schema unchanged.
9 unchanged entries
(schema root)cwdenvIdmodeonlyonly › [items]skipskip › [items]yes
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
39 tools with no recorded change
authcallCloudApidownloadTemplateenvDomainManagementmanageAgentsmanageAppAuthmanageAppsmanageCloudRunmanageDataModelmanageEnvmanageFunctionsmanageGatewaymanageHostingmanageLogsmanageMysqlDatabasemanagePermissionsmanagePgDatabasemanageStoragemodifyDataModelprepareFeedbackqueryAgentsqueryAppAuthqueryAppsqueryCloudRunqueryEnvqueryFunctionsqueryGatewayqueryHostingqueryLogsqueryMysqlDatabasequeryPermissionsqueryPgDatabasequeryPgStoragequeryStoragereadNoSqlDatabaseContentreadNoSqlDatabaseStructuresearchKnowledgeBasewriteNoSqlDatabaseContentwriteNoSqlDatabaseStructure
Evidence and provenance
- Static findings
- PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Automated static analysis. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
tencentcloudbase-cloudbase-mcp/2.37.5~2.37.6The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 11:28 PM UTC.- Distribution
npm- Previous release
@cloudbase/cloudbase-mcp@2.37.542 tools · published by the registry Nov 6, 2026, 7:38 AM UTCArtifact integritysha512-Ij2HbPcix9bFsnJn1P2Q/mBIIpc0727RW3bSwI1mUYP3shwT8GRhhD6ZbE1rxufGH/zR6Xcn5kaieRLprwTT9g==Interface fingerprintsha256:d1b49c1a3cfca090974d48103ae1ee729b09bd652430602809165f70d2a50145Exact interface snapshot (JSON)- Current release
@cloudbase/cloudbase-mcp@2.37.642 tools · published by the registry Nov 11, 2026, 8:10 AM UTCArtifact integritysha512-9C358nkf+4P8aeg6CJCHS7BvWV1UINCUPi+OKMO3kHRbDGHx9YZqOivF/9EoVdZTT90NFs3MoKTZKwDEC00Pug==Interface fingerprintsha256:496918b4106c619f232f4f04735fd9231e1dc164bcafd522e8e2c3399acebd72Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Informational
3 findingsdeployApplyINFOChangeddeployBuildINFOChangeddeployPlanINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.