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 #279] [MERGED] chore: version packages #285

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/279
Author: @llama-org-ci-bot[bot]
Created: 1/14/2026
Status: ✅ Merged
Merged: 1/14/2026
Merged by: @adrianlyjak

Base: main ← Head: changeset-release/main

📝 Commits (1)

📊 Changes

7 files changed (+16 additions, -10 deletions)

View changed files

➖ .changeset/add-workflow-classname.md (+0 -6)
📝 packages/llama-index-utils-workflow/CHANGELOG.md (+6 -0)
📝 packages/llama-index-utils-workflow/package.json (+1 -1)
📝 packages/llama-index-utils-workflow/pyproject.toml (+1 -1)
📝 packages/llama-index-workflows/CHANGELOG.md (+6 -0)
📝 packages/llama-index-workflows/package.json (+1 -1)
📝 packages/llama-index-workflows/pyproject.toml (+1 -1)

📄 Description

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

llama-index-utils-workflow@0.7.1

Patch Changes

  • 40be1c7: add workflow class name to WorkflowGraph representation

llama-index-workflows@2.12.1

Patch Changes

  • 40be1c7: add workflow class name to WorkflowGraph representation

🔄 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/279 **Author:** [@llama-org-ci-bot[bot]](https://github.com/apps/llama-org-ci-bot) **Created:** 1/14/2026 **Status:** ✅ Merged **Merged:** 1/14/2026 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `changeset-release/main` --- ### 📝 Commits (1) - [`9e318b4`](https://github.com/run-llama/workflows-py/commit/9e318b41c0f6fae50a0df5aac054443017d17675) chore: version packages ### 📊 Changes **7 files changed** (+16 additions, -10 deletions) <details> <summary>View changed files</summary> ➖ `.changeset/add-workflow-classname.md` (+0 -6) 📝 `packages/llama-index-utils-workflow/CHANGELOG.md` (+6 -0) 📝 `packages/llama-index-utils-workflow/package.json` (+1 -1) 📝 `packages/llama-index-utils-workflow/pyproject.toml` (+1 -1) 📝 `packages/llama-index-workflows/CHANGELOG.md` (+6 -0) 📝 `packages/llama-index-workflows/package.json` (+1 -1) 📝 `packages/llama-index-workflows/pyproject.toml` (+1 -1) </details> ### 📄 Description This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## llama-index-utils-workflow@0.7.1 ### Patch Changes - 40be1c7: add workflow class name to WorkflowGraph representation ## llama-index-workflows@2.12.1 ### Patch Changes - 40be1c7: add workflow class name to WorkflowGraph representation --- <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:08 -05:00
yindo closed this issue 2026-02-16 02:17:08 -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#285
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?