fix: correct release and repository links - #13
Conversation
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 263e188f58
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| json!({ | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "$id": "https://github.com/livenv/batch-git/schemas/operation-result-v1.json", | ||
| "$id": "https://github.com/ovaso/batch-git-rs/schemas/operation-result-v1.json", |
There was a problem hiding this comment.
Preserve the published v1 schema identities
For automation that registers or caches these public schemas by $id, changing the URI makes this a different schema resource even though the command still returns the v1 schema. The repository's architecture contract permits only new optional fields within the same major version, and the newly added contract text itself describes $id as stable, so consumers expecting the previously published livenv/batch-git identity can stop recognizing or resolving the schema after upgrading. Keep the old identifiers despite the repository move, or introduce the renamed identities under a new schema/API version rather than silently replacing both v1 IDs.
Useful? React with 👍 / 👎.
Summary / 变更说明
Validation / 验证
cargo fmt -- --checkcargo test --lockedcargo clippy --all-targets --all-features -- -D warningsRisk and rollback / 风险与回滚