[Bug]: llama-index-readers-upstage 0.2.1 version hasn't been updated

[cyzhzhd]

Bug Description

Hi Llama Index Team,

We've been working to update llama-index-readers-upstage to version 0.2.1, as outlined in this pull request. However, it appears the version has not been updated on PyPI.

Could you advise on any steps we might need to take, or if there’s any way we could facilitate updating the version on PyPI?

Thank you for your assistance!

Version

v0.11.21

Steps to Reproduce

1. install depedency pip install llama-index-readers-upstage
2. import UpstageDocumentParseReader

import os

os.environ["UPSTAGE_API_KEY"] = "YOUR_API_KEY"

from llama_index.readers.upstage import UpstageDocumentParseReader

file_path = "/PATH/TO/YOUR/FILE.pdf"

reader = UpstageDocumentParseReader()

# For improved memory efficiency, consider using the lazy_load_data method to load documents page by page.
docs = reader.load_data(file_path=file_path)

for doc in docs[:3]:
    print(doc)

and we've got ImportError for UpstageDocumentParseReader

Relevant Logs/Tracbacks

No response

[dosubot[bot]]

Hello @cyzhzhd 👋 I'm here to help you with any software bugs, questions, or contributions you have. Let's tackle this issue together while we wait for a human maintainer.

The issue you're experiencing with the llama-index-readers-upstage version not being updated on PyPI might be related to the CI/CD process for publishing packages. The repository does have CI/CD workflows that handle the deployment of packages to PyPI, specifically through scripts like publish_sub_package.yml and publish_release.yml. These scripts are triggered on certain events, such as pushes to the main branch or tag pushes matching a specific pattern, and they use Poetry for publishing ^[1][2].

To address the issue, you might want to check if the necessary triggers for these workflows have been activated. Ensure that the version tag v0.2.1 has been correctly pushed to the repository, as this would typically trigger the publish_release.yml workflow to publish the new version to PyPI. Additionally, verify that the PyPI token and other necessary secrets are correctly configured in the repository settings to allow for successful authentication and publishing.

If these steps have been followed and the issue persists, it might be worth reviewing the logs of the CI/CD workflows to identify any errors or issues during the publishing process.

To continue talking to Dosu, mention @dosu.

[logan-markewich]

The publish failed because two packages were updated -- one that depended on the other being updated first.

I've manually published the reader package just now https://pypi.org/project/llama-index-readers-upstage/