Skip to content

Keep the deprecated stream extension until 0.4.0 - #108

Closed
KamilSztandur wants to merge 1 commit into
after-first-unfocusfrom
deprecations-to-0-4
Closed

KamilSztandur wants to merge 1 commit into
after-first-unfocusfrom
deprecations-to-0-4

Conversation

@KamilSztandur

Copy link
Copy Markdown
Collaborator

Problem

AdvancedFieldController.stream, the migration bridge for 0.1.x cubit streams, says it will be removed in 0.3.0. The 0.3.0 release already asks users for one change, a default case in a switch over ValidationMode. Taking the bridge away in the same release would make apps that still compose streams pay twice for one upgrade.

Solution

The bridge stays one more minor version. The deprecation message, the migration guide (both the repo file and the docs page) and the FAQ now say 0.4.0. No code changes beyond the string.

Stacked on #103; merge after it.

🤖 Generated with Claude Code

It was announced for removal in 0.3.0. That release already asks users
for one change (a default case in a switch over ValidationMode), so the
bridge for 0.1.x cubit streams gets one more minor version. The
deprecation message, the migration guide and the FAQ say 0.4.0 now.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@KamilSztandur KamilSztandur mentioned this pull request Oct 24, 2026
@PiotrRogulski

Copy link
Copy Markdown
Member

Actually, I think it would be better to make breaking changes as one upgrade, instead of making users migrate twice 🤔

@KamilSztandur

Copy link
Copy Markdown
Collaborator Author

Dropped: the stream extension is removed in 0.3.0 as announced, in a separate PR.

@KamilSztandur
KamilSztandur deleted the deprecations-to-0-4 branch October 24, 2026 13:40
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