run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-20 19:57:02 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[PR #308] [MERGED] Add automated workflow to bump llama-index-core dependency #312

New Issue
Closed
opened 2026-02-16 02:17:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:17:12 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/308
Author: @adrianlyjak
Created: 1/26/2026
Status: ✅ Merged
Merged: 1/26/2026
Merged by: @adrianlyjak

Base: main ← Head: claude/add-dependency-bump-workflow-5QunR

📝 Commits (1)

  • 7f84c37 chore: add workflow to bump llama-index-core dependency

📊 Changes

1 file changed (+28 additions, -0 deletions)

View changed files

➕ .github/workflows/bump_llama_index_core.yml (+28 -0)

📄 Description

Summary

This PR introduces a new GitHub Actions workflow that automates the process of bumping the llama-index-core dependency across the repository. The workflow can be triggered either by a repository dispatch event (when llama-index-core is released) or manually via workflow dispatch.

Key Changes

  • New workflow file: .github/workflows/bump_llama_index_core.yml
    • Triggered on llama-index-core-release repository dispatch events
    • Supports manual triggering with optional specific version input
    • Automatically creates pull requests when version changes are detected

Implementation Details

  • Version detection: Extracts current and new versions from uv.lock file
  • Dependency update: Uses uv lock --upgrade-package to update the lock file
  • Change detection: Only creates a PR if the version actually changed
  • Authentication: Uses GitHub App token for PR creation to ensure proper CI/CD integration
  • PR metadata: Automatically generated PR includes:
    • Clear commit message with new version
    • Detailed body showing version transition
    • Relevant labels (dependencies, automated)
    • Link back to the workflow for traceability
  • Affected packages: Documents that llama-index-integration-tests and llama-index-utils-workflow are impacted

This automation reduces manual maintenance overhead and ensures the repository stays up-to-date with the latest llama-index-core releases.

https://claude.ai/code/session_01XmJV7dHRYt9Y2GvFY3qRw2

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/workflows-py/pull/308 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 1/26/2026 **Status:** ✅ Merged **Merged:** 1/26/2026 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `claude/add-dependency-bump-workflow-5QunR` --- ### 📝 Commits (1) - [`7f84c37`](https://github.com/run-llama/workflows-py/commit/7f84c37c92e7d4bf9c242fee5636cfdb3172b917) chore: add workflow to bump llama-index-core dependency ### 📊 Changes **1 file changed** (+28 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/bump_llama_index_core.yml` (+28 -0) </details> ### 📄 Description ## Summary This PR introduces a new GitHub Actions workflow that automates the process of bumping the `llama-index-core` dependency across the repository. The workflow can be triggered either by a repository dispatch event (when llama-index-core is released) or manually via workflow dispatch. ## Key Changes - **New workflow file:** `.github/workflows/bump_llama_index_core.yml` - Triggered on `llama-index-core-release` repository dispatch events - Supports manual triggering with optional specific version input - Automatically creates pull requests when version changes are detected ## Implementation Details - **Version detection:** Extracts current and new versions from `uv.lock` file - **Dependency update:** Uses `uv lock --upgrade-package` to update the lock file - **Change detection:** Only creates a PR if the version actually changed - **Authentication:** Uses GitHub App token for PR creation to ensure proper CI/CD integration - **PR metadata:** Automatically generated PR includes: - Clear commit message with new version - Detailed body showing version transition - Relevant labels (`dependencies`, `automated`) - Link back to the workflow for traceability - **Affected packages:** Documents that `llama-index-integration-tests` and `llama-index-utils-workflow` are impacted This automation reduces manual maintenance overhead and ensures the repository stays up-to-date with the latest `llama-index-core` releases. https://claude.ai/code/session_01XmJV7dHRYt9Y2GvFY3qRw2 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 02:17:12 -05:00
yindo closed this issue 2026-02-16 02:17:12 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#312
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?