文件最后提交记录最后更新时间
feat: idempotent migrate script modification and fix agent model error Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !653 merge develop-20260210 into develop feat: idempotent migrate script modification and fix agent model error Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind refactor **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!6533 个月前
fix : Add idempotent support for unique constraint operations in migrations Co-authored-by: cs123abc<chensheng63@huawei.com> # message auto-generated for no-merge-commit merge: !760 merge develop-20260228-v3 into develop fix : Add idempotent support for unique constraint operations in migrations Created-by: chensheng12345 Commit-by: cs123abc Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind fix **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes # **What scenarios were tested, and what were the verification results(Function, performance, reliability, etc.)**: * Need to describe clearly **Self-checklist**:(**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**) + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [x] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [x] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!7603 个月前