Skip to content

Conversation

@AstraBert
Copy link
Member

Attempt to add changesets + related CI actions for versioning and releasing (should be working)

Copy link
Contributor

@adrianlyjak adrianlyjak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments. Additionally, this hasn't replaced the existing publish/release workflow, so it will sort of conflict with the release process until that's resolved

I made a subsequent attempt to fix this up: #208

@@ -0,0 +1,19 @@
import toml # type: ignore [import]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the purpose of workflows-dev is to centralize these misc scripts in a package. Ideally the changesets code would go there too

@@ -0,0 +1,14 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should not be published

package.json Outdated
"scripts": {
"pre-commit-version": "pnpm changeset",
"version": "pnpm version-workflows-dev && pnpm version-llama-index-workflows && pnpm version-llama-index-utils-workflow",
"release": "pnpm release-workflows-dev && pnpm release-llama-index-workflows && pnpm release-llama-index-utils-workflow",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems rather roundabout.

  1. changesets calls release on the root workspace,
  2. the root workspace calls another script on all packages, manually defined
  3. each script calls the individual package script
  4. which calls a shared bash script

You could just jump straight from 1 to 4, and have the script iterate through all packages (or have them hard coded)

@@ -0,0 +1,2 @@
toml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are we using a requirements file? We're already using uv for dependency management

echo "Nothing to release"
exit 0
else
# build and publish llama_cloud_services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some copy pasta here

- name: Setup Python
uses: actions/setup-python@v5
with:
python-version: "3.11"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems rather old

@@ -0,0 +1,29 @@
import toml # type: ignore [import]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this test/validation doesn't seem very useful

* Switch to workflows-dev for changesets, remove old versioning

* trigger publish

* Remove more defunct things

* Fixup tests
@adrianlyjak adrianlyjak merged commit 704428f into adrian/multi-project Nov 17, 2025
16 checks passed
@adrianlyjak adrianlyjak deleted the clelia/changesets-attempt branch November 17, 2025 18:50
adrianlyjak added a commit that referenced this pull request Nov 17, 2025
* Make llama-index-workflows into a sub package

* Attempting to add changesets (#207)

---------

Co-authored-by: Clelia (Astra) Bertelli <133636879+AstraBert@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants