You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare PowerContext v1.5.2 with consistent installation references, generated API contracts, bilingual release notes, and a qualified Desktop contract identity.
What changes are included in this PR?
Synchronize managed release references and the upgrade target to 1.5.2 through make version-bump.
Regenerate Python API metadata, Dify's tool contract, and Desktop contract digests.
Add English and Chinese GitHub Release notes and the website changelog dated 2026-11-16, covering performance, native Dashboard observability, Desktop setup, directory plugins, Gateway subscription transports, and cross-tool handoffs.
Add a Desktop compatibility record backed by four real built-wheel SQLite Server protocol scenarios. Preserve historical qualification records.
Retain the existing upgrade-required policy and complete publication acceptance matrix.
Are there any user-facing changes?
Installation instructions target v1.5.2. Release notes explain the replacement of the previous managed plugin framework and the migration refusal when old plugin registrations or data remain. Closed-unmerged PRs and design-only proposals are excluded from delivered features.
The performance figures use the release brief's supplied comparison with v1.5.1; this preparation did not rerun those benchmarks. Preparing this PR does not tag or publish packages, qualify Desktop installers, or establish formal installed-release upgrade acceptance.
How was this change tested?
make version-bump VERSION=1.5.2 and make release-check VERSION=1.5.2: passed.
make check and uv run prek run -a: passed.
Release-version, upgrade-policy, API and JS regression tests: 209 passed, 1 environment-gated skip.
make contract-test: 69 passed.
Dify contract generation check and Desktop generate:check: passed.
make docs-test: passed, including 36 website tests, production compilation, TypeScript checking, and verification of 1,116 public pages and internal links.
Desktop built-wheel SQLite protocol qualification: anonymous, Bearer, HTTPS/base-path, and enforced-provider modes passed. The host lacks WebKitGTK 4.1, so the unchanged native protocol modules and probe were compiled in an isolated Cargo crate using dependency versions and checksums from the product lock, without the Tauri shell or ci-fixtures. A local harness wrapper allowed 60 seconds for Server startup after the original polling budget timed out; request timeouts and protocol assertions were unchanged. Full evidence and limits are recorded in desktop/VALIDATION.md.
The formal release upgrade matrix and external-provider performance benchmarks were not run for this preparation.
AI usage statement
OpenAI Codex assisted with release preparation, bilingual release notes, contract generation, validation, and PR preparation.
The release notes say of databases with old plugin registrations: "export and remove them using the previous version before upgrading" / "升级前需使用旧版本导出并移除这些内容". From reading 1.5.1, I do not think that can be done with supported operations: unload keeps the registration identity and the family schemas (see the comment in artifact_storage_readiness.py), and I found nothing that deletes pc_artifact_family_schemas rows, so the v1_5_0_005 preflight still refuses after unloading. I have not tested this against an installed 1.5.1. If it is right, a more accurate sentence would be that such databases cannot be upgraded in place and should stay on 1.5.1 or move to a new database. Only databases that loaded plugins of the previous framework are affected. @frf12 does this match your understanding?
Before publication, docs/en/development/releasing.md and docs/zh/development/releasing.md still describe the shared migration chain as ending at v1_5_0_004, and the publication example still uses powercontext-v1.5.1.
The operator guides in this PR now end both source paths at v1_5_0_005. The “Verify before publication” section should use that same head, and the workflow example should use powercontext-v1.5.2. These files are not part of this diff, so this note is on the pull request rather than a line comment.
#2672 also edits this chain. Pick one place to update it so the two pulls do not each rewrite the same paragraph.
On the last point: #2672 is closed, so this PR is the only place that edits the chain. If it helps, the releasing.md change is the two-line edit in 857e38cdd on jasper-yl:docs/migration-v1-5-0-005 (... → v1_5_0_004 to ... → v1_5_0_004 → v1_5_0_005 in both locales); it does not touch the powercontext-v1.5.1 workflow example.
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
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.
Which issue or RFC does this PR close?
Release preparation for the merged PRs labeled 1.5.2. No issue is closed by this preparation PR.
Rationale for this change
Prepare PowerContext v1.5.2 with consistent installation references, generated API contracts, bilingual release notes, and a qualified Desktop contract identity.
What changes are included in this PR?
make version-bump.upgrade-requiredpolicy and complete publication acceptance matrix.Are there any user-facing changes?
Installation instructions target v1.5.2. Release notes explain the replacement of the previous managed plugin framework and the migration refusal when old plugin registrations or data remain. Closed-unmerged PRs and design-only proposals are excluded from delivered features.
The performance figures use the release brief's supplied comparison with v1.5.1; this preparation did not rerun those benchmarks. Preparing this PR does not tag or publish packages, qualify Desktop installers, or establish formal installed-release upgrade acceptance.
How was this change tested?
make version-bump VERSION=1.5.2andmake release-check VERSION=1.5.2: passed.make checkanduv run prek run -a: passed.make contract-test: 69 passed.generate:check: passed.make docs-test: passed, including 36 website tests, production compilation, TypeScript checking, and verification of 1,116 public pages and internal links.ci-fixtures. A local harness wrapper allowed 60 seconds for Server startup after the original polling budget timed out; request timeouts and protocol assertions were unchanged. Full evidence and limits are recorded indesktop/VALIDATION.md.The formal release upgrade matrix and external-provider performance benchmarks were not run for this preparation.
AI usage statement
OpenAI Codex assisted with release preparation, bilingual release notes, contract generation, validation, and PR preparation.