:octopus: Exposed release candidate <1.0.0-rc-3> i...
# exposedo
Oleg Babichev
11/06/2025, 8:14 PM🐙 Exposed release candidate 1.0.0-rc-3 is now released 🐙
exposed 5
K 13
y
y9san9
11/10/2025, 4:25 PMIs it reasonable that we are going to have 1.0.0 stable release where I have a single file reproducer where SchemaUtils don't work?
n
Neon
11/10/2025, 5:05 PMIn addition to the fact that nullable fields don't seem to get along with r2dbc and batch*/upsert queries
👆 1
o
Oleg Babichev
11/27/2025, 10:36 AM@y9san9 I would say it's reasonable, cause the main goal of 1.0.0 release is stabilizing Exposed API and keep support (ideally) without breaking changes for the whole 1.0.0 after the release.
That's why we're working mostly on bugfixing and refactorings rights now rather than adding new features.
y
y9san9
12/02/2025, 8:32 AM@Oleg Babichev hi, thank you for reply. The problem is with existing features. It may be a good choice to remove schema utils for 1.0.0 since they don't work anyways
o
Oleg Babichev
12/05/2025, 11:38 AM@y9san9 Schema utils could be quite week in terms of proper migration tool, but we know that there many people who use it for testing purposes (inside Exposed we also do that actually), or for generating migration scripts that could be used with other migration tools like flyway later.
Could you remind which issues you're talking about? I could check it in the nearest time. I checked YouTrack but found only one issue from you, the one about problems with transaction context.. I expect it could be in Slack, but can't find right now.
7 Views