Skip to content

remove experimental v2 from expressions#291

Open
nathanbegbie wants to merge 2 commits into
developfrom
remove-experimental-v2-of-expressions
Open

remove experimental v2 from expressions#291
nathanbegbie wants to merge 2 commits into
developfrom
remove-experimental-v2-of-expressions

Conversation

@nathanbegbie
Copy link
Copy Markdown
Member

smn
smn previously approved these changes Nov 10, 2025
Copy link
Copy Markdown
Contributor

@smn smn left a comment

Choose a reason for hiding this comment

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

Happy! But i suspect somewhere internally in our app we may still be hitting some V2 compat module stuff but we can deal with that when we merge in the version that drops the V2 support.

Please do make sure that when you do release you do a major version bump.

@nathanbegbie
Copy link
Copy Markdown
Member Author

@davidkhk just flagging - when I'm back from leave, let's coordinate on this one and getting it in to the engage repo

@nathanbegbie
Copy link
Copy Markdown
Member Author

@nathanbegbie
Copy link
Copy Markdown
Member Author

Once we merge in #305, and we're happy it works, I'll make the breaking change release and get this done. Sorry it's taken so long!

@nathanbegbie
Copy link
Copy Markdown
Member Author

I'm now okay with the release process, so will be doing this with the tiny slice of my Friday that can be called calm

@nathanbegbie nathanbegbie force-pushed the remove-experimental-v2-of-expressions branch from f1d8050 to 69119d8 Compare January 23, 2026 06:45
Removal of these modules consitutes a breaking change, so we're doing a major version bump
@nathanbegbie
Copy link
Copy Markdown
Member Author

Just noting that I'm going to bump the version number in this PR as well and do a relase as soon as I merge

@smn
Copy link
Copy Markdown
Contributor

smn commented Jan 23, 2026

Have we confirmed nothing in Turn relies on the Expression.v2 module anywhere?

@nathanbegbie
Copy link
Copy Markdown
Member Author

@smn Ah, I was going to make the release, then sort that out downstream in another PR, but probs make sense to do that check before making a blocking release.

Doing that now

@smn
Copy link
Copy Markdown
Contributor

smn commented Jan 23, 2026

well you can tell another repo to just pull the dependency as code from this repo using the github: stuff in mix.exs -- may save a bunch of round trips between releases to get an answer to this?

@nathanbegbie
Copy link
Copy Markdown
Member Author

nathanbegbie commented Jan 23, 2026

Happy! But i suspect somewhere internally in our app we may still be hitting some V2 compat module stuff but we can deal with that when we merge in the version that drops the V2 support.

Please do make sure that when you do release you do a major version bump.

@smn hang on a minute, you were the one who suggested that approach ☝️ 😂

@nathanbegbie
Copy link
Copy Markdown
Member Author

and in flow_runner:

% git grep "Expression.V2"
lib/flow_runner.ex:  alias Expression.V2.Compat
lib/flow_runner/custom_blocks/dynamic_select_one_response.ex:  alias Expression.V2.Compat

@smn
Copy link
Copy Markdown
Contributor

smn commented Jan 23, 2026

@smn hang on a minute, you were the one who suggested that approach ☝️ 😂

heh, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants