-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
ci: create a nightly build workflow #3553
Conversation
Pull Request Validation ReportThis comment is automatically generated by Conventional PR Whitelist Report
Result Pull request does not satisfy any enabled whitelist criteria. Pull request will be validated. Validation Report
Result Pull request satisfies all enabled pull request rules. Last Modified at 26 Aug 24 18:34 UTC |
This pull request is automatically being deployed by Amplify Hosting (learn more). |
ac543dc
to
36b4ae3
Compare
build_docker_main: false | ||
nightly_tag: ${{ needs.create-nightly-tag.outputs.TAG }} | ||
|
||
# slack-notification: |
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 wonder if we should push on Discord instead of Slack, since the community is there. This would encourage external contributiors to add integration tests when they add new components and make them as involved as the langflow core maintainers
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.
Agreed. Will do this either in a follow up, or here if it's not reviewed in the next few days.
Detected 54 changes to dependencies in Poetry lockfileAdded aenum (3.1.15) (3 added, 0 removed, 51 updated, 426 not changed) |
9ea0a26
to
484517d
Compare
# + ".dev" | ||
# + "0" | ||
# + datetime.now(pytz.timezone("UTC")).strftime("%Y%m%d") | ||
# ) |
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.
Note this. The current versioning uses X.Y.Z.devN
- this is a lot easier to work with when iterating, as you can just increment N
, but I see the appeal of the date-based name once builds are stable here. We can push this for now, ensure it's working in the next few iterations, yank the .devN
builds, then move to date-based.
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 like the date-based as well and agree that we can change that later
# the langflow-base dependency in pyproject.toml _again_. This is redundant, but | ||
# necessary because the release workflow relies on that script to update the base | ||
# dependency. | ||
pattern = re.compile(r'langflow-base = \{ path = "\./src/backend/base", develop = true \}') |
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.
This is worth noting. Didn't want to make changes to the release workflow in this PR since it's already a mess, but we can simplify some of this.
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.
By using uv instead of poetry? hahahah
Just kidding.
raise ValueError(f"Invalid build type: {build_type}") | ||
|
||
|
||
if __name__ == "__main__": |
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 should add tests for these scripts :)
package_name = "Langflow Base" | ||
except ImportError as e: | ||
logger.exception(e) | ||
raise e |
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.
Logic moved into version.py
and simplified to handle the four build types now
|
||
# TODO: FRAZ - Figure out what I want the behavior to be for nightly builds |
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.
TODO: Based on the code, I suspect we are just logging a warning that will say:
Your version of langflow (<some nightly version>) is outdated. Please update to <latest stable>
Which, doesn't really make sense - we probably want it to say "there's a new nightly build to try" or even just ignore this since it's already known you're on a nightly build, but low priority either way I believe. Not a blocker for this PR.
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'd say we just ignore it
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
cba272d
to
3bfcc73
Compare
3bfcc73
to
5d03c88
Compare
7a5b818
to
c2c5c29
Compare
This PR is the beginning of nightly builds. It adds the following:
X.Y.Z.devN
nightly_release
workflow thatFollow ups are noted in comments:
I've tested that I can download the latest nightly build and run langflow as normal.
langflow-nightly
depends on the version oflangflow-base-nightly
at the time of release.