mirror of
https://github.com/lancedb/lancedb.git
synced 2025-12-22 21:09:58 +00:00
chore: update lance dependency to v0.38.3-beta.7 (#2735)
## Summary - bump Lance dependencies to v0.38.3-beta.7 - ran cargo clippy --workspace --tests --all-features -- -D warnings - ran cargo fmt --all Triggered by tag [v0.38.3-beta.7](https://github.com/lancedb/lance/releases/tag/v0.38.3-beta.7). --------- Co-authored-by: LanceDB Robot <robot@lancedb.com>
This commit is contained in:
committed by
GitHub
parent
845641c480
commit
92a4e46f9f
@@ -95,8 +95,9 @@ jobs:
|
||||
5. Create and switch to a new branch named "${BRANCH_NAME}" (replace any duplicated hyphens if necessary).
|
||||
6. Stage all relevant files with "git add -A". Commit using the message "chore: update lance dependency to v${VERSION}".
|
||||
7. Push the branch to origin. If the branch already exists, force-push your changes.
|
||||
8. Create a pull request targeting "main" with title "chore: update lance dependency to v${VERSION}". In the body, summarize the dependency bump, clippy/fmt verification, and link the triggering tag (${TAG}). Use the GitHub CLI if helpful.
|
||||
9. After creating the PR, display the PR URL, "git status --short", and a concise summary of the commands run and their results.
|
||||
8. env `GH_TOKEN` is available, use `gh` tools for github related operations like creating pull request.
|
||||
9. Create a pull request targeting "main" with title "chore: update lance dependency to v${VERSION}". In the body, summarize the dependency bump, clippy/fmt verification, and link the triggering tag (${TAG}).
|
||||
10. After creating the PR, display the PR URL, "git status --short", and a concise summary of the commands run and their results.
|
||||
|
||||
Constraints:
|
||||
- Use bash commands; avoid modifying GitHub workflow files other than through the scripted task above.
|
||||
|
||||
Reference in New Issue
Block a user