-
Notifications
You must be signed in to change notification settings - Fork 36
edits #208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
edits #208
Conversation
4a6f27c to
c9e6475
Compare
c9e6475 to
70eeb20
Compare
AstraBert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, this is way cleaner :))
| "name": "llama-index-utils-workflow", | ||
| "version": "0.5.0", | ||
| "private": "true", | ||
| "private": "false", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if public or private makes a big difference here, since we don't publish this as a JS package nevertheless, but the ratio behind setting it as private is because this is not a JS package and should not be interpreted as such by changesets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release process is completely run by our script, so this doesn't get published.
Maybe silly, but I'm reading the package.json private value in changesets.py to infer whether the package should be published (Could instead just treat all folders with both pyproject.toml and package.json as ones that should be published)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah, makes sense then, fine to keep it as public :))
No description provided.