run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-19 16:43:32 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

[PR #941] [MERGED] chore: version packages #968

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_cloud_services/pull/941
Author: @github-actions[bot]
Created: 10/3/2025
Status: ✅ Merged
Merged: 10/3/2025
Merged by: @adrianlyjak

Base: main ← Head: changeset-release/main

📝 Commits (1)

📊 Changes

7 files changed (+18 additions, -11 deletions)

View changed files

➖ .changeset/nasty-jeans-fall.md (+0 -6)
➕ py/CHANGELOG.md (+7 -0)
📝 py/llama_parse/pyproject.toml (+2 -2)
📝 py/package.json (+1 -1)
📝 py/pyproject.toml (+1 -1)
📝 ts/llama_cloud_services/CHANGELOG.md (+6 -0)
📝 ts/llama_cloud_services/package.json (+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-cloud-services@0.3.7

Patch Changes

  • d028397: Update llama-cloud api version, and integrate with agent data deletion

llama-cloud-services-py@0.6.56

Patch Changes

  • d028397: Update llama-cloud api version, and integrate with agent data deletion

🔄 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/llama_cloud_services/pull/941 **Author:** [@github-actions[bot]](https://github.com/apps/github-actions) **Created:** 10/3/2025 **Status:** ✅ Merged **Merged:** 10/3/2025 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `changeset-release/main` --- ### 📝 Commits (1) - [`f6c0b70`](https://github.com/run-llama/llama_cloud_services/commit/f6c0b70ea8769711454027f475478f453f3459e4) chore: version packages ### 📊 Changes **7 files changed** (+18 additions, -11 deletions) <details> <summary>View changed files</summary> ➖ `.changeset/nasty-jeans-fall.md` (+0 -6) ➕ `py/CHANGELOG.md` (+7 -0) 📝 `py/llama_parse/pyproject.toml` (+2 -2) 📝 `py/package.json` (+1 -1) 📝 `py/pyproject.toml` (+1 -1) 📝 `ts/llama_cloud_services/CHANGELOG.md` (+6 -0) 📝 `ts/llama_cloud_services/package.json` (+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-cloud-services@0.3.7 ### Patch Changes - d028397: Update llama-cloud api version, and integrate with agent data deletion ## llama-cloud-services-py@0.6.56 ### Patch Changes - d028397: Update llama-cloud api version, and integrate with agent data deletion --- <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 00:19:42 -05:00
yindo closed this issue 2026-02-16 00:19:42 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
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/llama_cloud_services#968
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?