Skip to content

fix: correct release and repository links - #13

Merged
ovaso merged 1 commit into
mainfrom
codex/fix-release-links
Aug 7, 2026
Merged

fix: correct release and repository links#13
ovaso merged 1 commit into
mainfrom
codex/fix-release-links

Conversation

@ovaso

@ovaso ovaso commented Aug 7, 2026

Copy link
Copy Markdown
Owner

Summary / 变更说明

Validation / 验证

  • cargo fmt -- --check
  • cargo test --locked
  • cargo clippy --all-targets --all-features -- -D warnings
  • Both language versions of relevant documentation, JSON contracts, and changelogs are updated / 相关中英文文档、JSON 契约与两份 CHANGELOG 已更新

Risk and rollback / 风险与回滚

@ovaso

ovaso commented Aug 7, 2026

Copy link
Copy Markdown
Owner Author

@codex review

@ovaso
ovaso merged commit 6fac4f6 into main Aug 7, 2026
7 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread README.md
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",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant