chore(release): prepare 1.17.0 - #169
Merged
Merged
Conversation
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.
Summary
1.17.0changelog for native Managed Agent Deployments, CLI language switching, and Free Tier Auto-Stop fixeslanguageconfiguration in the English and Chinese root/npm READMEsbailian-clihub Skill while keeping generated command details inreference/config.md1.17.0versions across all five packages and Bailian SkillsVerification
vp check— 0 errors (5 existing warnings)vp test packages/runtime/tests/i18n.test.ts packages/commands/tests/config-ui.test.ts— 17 passedpnpm run sync:skill-assets— generated references and Skill versions are synchronizedCI=true node tools/release/publish-channel.mjs --channel test --knowledge --dry-run— five-package build, pack, publint, and gitleaks checks passedgit diff --checkpassedTest note
A full
vp testrun was attempted. It entered live service-backed E2E suites and produced unrelated environment/service failures across knowledge, media generation, quota, and other integrations, then remained running and was stopped. The directly affected localization tests and the complete release dry-run passed.