Skip to content

Publish refs as a global for 0.10 compatibility - #7806

Merged
masenf merged 3 commits into
mainfrom
fix/refs-compat-shim
Nov 11, 2026
Merged

masenf merged 3 commits into
mainfrom
fix/refs-compat-shim

Conversation

@masenf

@masenf masenf commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

All Submissions:

  • Have you followed the guidelines stated in CONTRIBUTING.md file?
  • Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • This change requires a documentation update

Changes To Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully ran tests with your changes locally?

Release fix-up for FINDING-003 and the reflex half of FINDING-002 from the reflex 0.11.0a1 pre-release testing (artifacts on branch claude/vibrant-pasteur-3921g3 of reflex-dev/reflex, prerelease-testing/runs/2026-11-11-v0.11.0a1/).

Defect

FINDING-003: ReferenceError: refs is not defined. On 0.10.1, Component._get_hooks_imports imported refs from $/utils/state into every module that had an id'd component, because the old ref hook wrote refs['ref_x'] = ref_x during render. #7694 replaced that hook with useRegisteredRef and now imports only that. Any code that reads refs[...] without declaring the import throws on 0.11.0a1, in dev and prod and in every auto_memoize × react_compiler cell. Affected code:

  • reflex-enterprise AG Grid API vars (grid.api.*, AgGridAPI.create(id)) and aligned_grids (HIGH; fixed in rxe as well, see the linked PR).
  • a custom component whose add_hooks string reads refs[...];
  • a raw rx.Var("() => refs[...]").to(FunctionVar) handler, and rx.call_function on such a Var.

FINDING-002 (reflex side): deploy_url now defaults to None. The breaking-change fragment never told code that reads config.deploy_url what to use instead. reflex-enterprise's MCPPlugin died at prod startup because of this.

Fix

  • state.js publishes the registry as a global: globalThis.refs = refs. An unbound refs[...] in an add_hooks string, a raw Var handler or rx.call_function resolves to the global, in every module and with any auto_memoize setting. A module that binds its own refs (an import { refs } or a const refs in add_custom_code) shadows the global. It does not conflict with it.

  • No implicit refs import is added to page or memo modules. An earlier head of this PR imported refs into every page and memo module. That broke code that declares its own refs: the duplicate binding is a parse error. In dev, React Router parses every route module, so one such import returned HTTP 500 for every route. reflex export failed. One const refs in a module also broke unrelated pages whose auto-memo wrappers mirror into the same app_components module.

  • refs is declared internal. The state.js comment, docs/wrapping-react/custom-code-and-hooks.md and the changelog say that refs is an internal implementation detail with no compatibility guarantee. They point users at public event actions (rx.set_value, rx.set_focus, rx.scroll_to), not at the private Var._as_ref(). The global exists only so code written against 0.10 keeps working in 0.11.

  • News fragments:

    • news/+refs-compat-import.misc.md: new.
    • packages/reflex-base/news/+react-compiler-generated-code.feature.md: one added sentence on refs being internal.
    • packages/reflex-base/news/+deploy-url-default.breaking.md: now tells deploy_url readers to use config.frontend_url (frontend origin), or config.api_url when the backend serves the frontend (single-port --env prod).

    Both reflex-base edits correct unreleased 0.11.0a1 fragments on main. news/+cors-prod-default.breaking.md is untouched (Accept the backend's own origin behind a TLS-terminating proxy #7799 is editing it).

React Compiler: generated modules do not import or write refs during render, so the compiler sees no new code. A prod run with react_compiler=True passes every case below. The _c(n) counts were not measured again after the change to a global.

Test plan

Regression test, written first and failing on the earlier head of this PR (1b1d786), which imported refs into every module:

  • tests/units/compiler/test_compiler.py::test_custom_code_may_declare_refs[auto_memoize True|False]: a page with an id'd input, an auto-memoized button, a component whose add_custom_code declares const refs = {}, and an rx.memo that holds that component. The page module, the legacy _compile_page output and every memo module hold the declaration but import no refs. 2 failed before, 2 pass after.
  • tests/units/components/test_component.py::test_ref_hook_registers_through_state_helper again expects only useRegisteredRef.
  • The global itself has no unit test: tests/js cannot import state.js, because its runtime dependencies are not installed there. The live app below covers it.
  • The deploy_url fragment change has no test.

Local results (targeted):

  • tests/units/compiler/test_compiler.py and the ref hook test: 94 passed.
  • pre-commit run on the changed files passes: ruff, pyright, ty, biome, update-pyi-files. No component signatures changed, so pyi_hashes.json is unchanged.

End to end in a small app, one route per case, driven in Chromium:

Case Earlier head (1b1d786) This head
raw Var handler reading refs['ref_target'] legacy ok legacy ok
add_hooks reading refs[...] without the import hook ok hook ok
hook built from Var._as_ref() as_ref ok as_ref ok
add_custom_code: import { refs } from "$/utils/state" dev HTTP 500 on every route renders
add_custom_code: const refs = {...} (page, page with id, rx.memo) page fails to load; reflex export exits 1 renders
plain memo / page sharing the memo module above fails to load renders
explicit add_imports({"$/utils/state": ["refs"]}), hook-local const refs = useRef() renders renders

Dev (default config) and --env prod with react_compiler=True both pass on this head. On 2d71015 (main before this PR) the raw Var handler fails with refs is not defined.

Notes

  • The compatibility shim is one global in state.js. A later minor can remove it once downstream code no longer reads refs[...]. A deprecation warning for raw refs[...] usage is out of scope here, because the compiler cannot detect such strings cheaply.
  • Companion reflex-enterprise PR (MCP prod startup, MCP consent redirect, AG Grid refs): linked in a comment below.

Generated by Claude Code

View guided diff Turn on auto-fix

Code that reads `refs[...]` without declaring the import (a raw Var event
handler, `rx.call_function` on a JS Var, a custom component's `add_hooks`
string, and reflex-enterprise's AG Grid API vars) worked on 0.10.1 because
`Component._get_hooks_imports` imported `refs` into every module with an id'd
component. #7694 replaced that hook with `useRegisteredRef` and dropped the
import, so these now throw `ReferenceError: refs is not defined`.

Restore the import next to `useRegisteredRef`, and add it to the base imports
of every page and memo module, so the add_hooks case also works where the hook
lands in a wrapper with no id'd component (auto_memoize=False). An unused or
read-only import has no React Compiler cost; only the render-time write that
#7694 moved did.

Declare `refs` internal in the state.js export comment, the wrapping-react
hooks docs and the changelog: components should reference a ref with
`Var._as_ref()`, whose var data carries the import. Also tell readers of
`config.deploy_url` that it can now be None (FINDING-002).

FINDING-003 / FINDING-002 from the reflex 0.11.0a1 pre-release testing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
@masenf
masenf requested review from a team and Alek99 as code owners November 11, 2026 08:54
@masenf masenf added this to the v0.11.0 milestone Nov 11, 2026
@masenf masenf added the on deck PRs lined up to review / merge next label Nov 11, 2026
@masenf

masenf commented Nov 11, 2026

Copy link
Copy Markdown
Collaborator Author

Companion reflex-enterprise PR: https://github.com/reflex-dev/reflex-enterprise/pull/290. It fixes MCP prod startup without deploy_url (FINDING-002), the MCP consent redirect in dev (FINDING-008), and the AG Grid refs import via Var._as_ref() (FINDING-003). It was verified end to end against PyPI reflex 0.11.0a1 and 0.10.1.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi


Generated by Claude Code

@greptile-apps

greptile-apps Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable new issue was found.

Summary

The PR restores access to refs for older custom hooks and raw Var expressions by publishing it on globalThis.

  • Older frontend code can still read the refs registry.
  • The deploy URL note tells callers which URL to use instead.

Reviews (4) · Last reviewed commit: "fix: publish refs as a global instead of..." · Reviewed by Greptile

Comment thread reflex/compiler/compiler.py Resolved
masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

All reported issues were addressed across 9 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread reflex/compiler/compiler.py Resolved
@codspeed

codspeed Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Merging this PR will degrade performance by 3.11%

2 warnings

⚠️ 18 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ 3 benchmarks with a significant change ran on different hardware

Their base and head results were measured on machines with a different CPU, core count or memory, so the changes might not come from the code. Run base and head on the same runner type.

Learn more about Macro Runners

See affected benchmarks

⚡ 1 improved benchmark
❌ 2 regressed benchmarks
✅ 148 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Benchmark BASE HEAD Efficiency
❌ test_state_collection_assignment[1000] 10.9 ms 12 ms -9.12%
❌ test_process_event_burst_independent_tokens[1] 2.7 ms 2.8 ms -4.5%
⚡ test_state_collection_assignment[100000] 1.1 s 1 s +4.81%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing fix/refs-compat-shim (5fed4a4) with main (34f8c3c)

Open in CodSpeed

`_compile_single_memo_function` built its imports from the function's own
imports only, so a raw-Var function memo body reading `refs[...]` without
declaring the import still threw in an unmirrored (one file per memo) module.
Merge `_MEMO_BASE_IMPORTS` there as well, so every memo module imports `refs`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
@masenf

masenf commented Nov 11, 2026

Copy link
Copy Markdown
Collaborator Author

CodSpeed is red here, but this PR doesn't cause it:

  • test_process_event_burst_independent_tokens[1]: -4.6%
  • test_arithmetic_operations[state]: -4.2%
  • test_arithmetic_operations[bare]: -4.1%

CodSpeed flags all three as measured on different hardware for base and head. The event-burst one shows the same 4–5% drop on every PR in this batch. This PR only adds refs to the import dicts of compiled page and memo modules. Neither event processing nor var arithmetic goes through the compiler, and the previous run on f714343 (same import change minus function memos) reported no performance change. CodSpeed is not a required check; leaving it for acknowledgement on CodSpeed.


Generated by Claude Code

The implicit `refs` import in every page and memo module collided with
custom code that binds its own `refs` (a module-level `const refs` or an
explicit `import { refs }` in add_custom_code). The duplicate binding is a
parse error: dev returned HTTP 500 for every route, and `reflex export`
failed. One such component also broke unrelated pages whose auto-memo
wrappers share its mirrored module.

state.js now sets `globalThis.refs = refs`. An unbound `refs[...]` in a
hook string or raw Var resolves to the global, and a module's own `refs`
shadows it. The per-module import shim in the compiler and the ref hook is
removed.

The docs and news no longer point users at the private `Var._as_ref()`;
they name the public event actions instead.
@FarhanAliRaza FarhanAliRaza changed the title Import refs into every page and memo module for 0.10 compatibility Publish refs as a global for 0.10 compatibility Nov 11, 2026
masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

1 issue found across 8 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/reflex-base/src/reflex_base/.templates/web/utils/state.js">

<violation number="1" location="packages/reflex-base/src/reflex_base/.templates/web/utils/state.js:71">
P2: This unconditionally overwrites the host page's `globalThis.refs`, so embedded or multiple-frontend deployments can lose an existing registry or resolve compatibility hooks against another app's refs. Publish the compatibility binding through a collision-safe, app-scoped mechanism instead of taking the generic global name.</violation>
</file>

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

// code written against 0.10 that reads `refs[...]` without the import keeps
// working; a module that binds its own `refs` shadows the global.
export const refs = {};
globalThis.refs = refs;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2: This unconditionally overwrites the host page's globalThis.refs, so embedded or multiple-frontend deployments can lose an existing registry or resolve compatibility hooks against another app's refs. Publish the compatibility binding through a collision-safe, app-scoped mechanism instead of taking the generic global name.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/reflex-base/src/reflex_base/.templates/web/utils/state.js, line 71:

<comment>This unconditionally overwrites the host page's `globalThis.refs`, so embedded or multiple-frontend deployments can lose an existing registry or resolve compatibility hooks against another app's refs. Publish the compatibility binding through a collision-safe, app-scoped mechanism instead of taking the generic global name.</comment>

<file context>
@@ -63,11 +63,12 @@ const TOKEN_KEY = "token";
+// code written against 0.10 that reads `refs[...]` without the import keeps
+// working; a module that binds its own `refs` shadows the global.
 export const refs = {};
+globalThis.refs = refs;
 
 /**
</file context>

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Not changing this. The global exists only so 0.10-era code that reads the bare identifier refs[...] resolves. A collision-safe or app-scoped name such as globalThis.__reflex_refs would not be found by that code, so the shim would no longer do its job.

As for collisions:

  • An iframe-embedded app has its own globalThis.
  • Two Reflex frontends can't share one window anyway: the router, socket and window.__reflex state are per window.
  • A module that binds its own refs still shadows the global, which was the reason for this change.

The remaining case is a host page that defines its own window.refs in the same window as a Reflex app. That page would have conflicted with 0.10's generated code too.


Generated by Claude Code

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Correction to my reply above: I was wrong that two Reflex frontends can't share a window. Embed mode (entry.client.embed.js, MOUNT_TARGET) mounts a Reflex app into a host page with a memory router, so two embedded Reflex apps can live in the same window. There, the second app's state.js replaces globalThis.refs, and the first app's 0.10-style code that reads bare refs[...] would resolve against the second app's registry. Framework code isn't affected, since it imports refs through Var._as_ref().

No bare global name can serve two apps in one window. The available options:

  • globalThis.refs ??= refs stops it from overwriting a host page's own refs. With two embedded apps, though, the second app's legacy reads would hit the first app's registry instead.
  • Accept the limitation and document it: legacy bare refs[...] works for a single app per window.

This is the reviewer's design call, so I'm leaving the thread open rather than resolving it.


Generated by Claude Code

Comment thread news/+refs-compat-import.misc.md Resolved
masenf pushed a commit that referenced this pull request Nov 11, 2026

@masenf masenf left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

looks good to me

masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
@masenf
masenf merged commit 381da0f into main Nov 11, 2026
167 of 168 checks passed
@masenf
masenf deleted the fix/refs-compat-shim branch November 11, 2026 18:46
masenf added a commit that referenced this pull request Nov 11, 2026
* Import refs into every page and memo module for 0.10 compatibility

Code that reads `refs[...]` without declaring the import (a raw Var event
handler, `rx.call_function` on a JS Var, a custom component's `add_hooks`
string, and reflex-enterprise's AG Grid API vars) worked on 0.10.1 because
`Component._get_hooks_imports` imported `refs` into every module with an id'd
component. #7694 replaced that hook with `useRegisteredRef` and dropped the
import, so these now throw `ReferenceError: refs is not defined`.

Restore the import next to `useRegisteredRef`, and add it to the base imports
of every page and memo module, so the add_hooks case also works where the hook
lands in a wrapper with no id'd component (auto_memoize=False). An unused or
read-only import has no React Compiler cost; only the render-time write that

Declare `refs` internal in the state.js export comment, the wrapping-react
hooks docs and the changelog: components should reference a ref with
`Var._as_ref()`, whose var data carries the import. Also tell readers of
`config.deploy_url` that it can now be None (FINDING-002).

FINDING-003 / FINDING-002 from the reflex 0.11.0a1 pre-release testing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

* Import refs into standalone function memo modules too

`_compile_single_memo_function` built its imports from the function's own
imports only, so a raw-Var function memo body reading `refs[...]` without
declaring the import still threw in an unmirrored (one file per memo) module.
Merge `_MEMO_BASE_IMPORTS` there as well, so every memo module imports `refs`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

* fix: publish refs as a global instead of importing it into every module

The implicit `refs` import in every page and memo module collided with
custom code that binds its own `refs` (a module-level `const refs` or an
explicit `import { refs }` in add_custom_code). The duplicate binding is a
parse error: dev returned HTTP 500 for every route, and `reflex export`
failed. One such component also broke unrelated pages whose auto-memo
wrappers share its mirrored module.

state.js now sets `globalThis.refs = refs`. An unbound `refs[...]` in a
hook string or raw Var resolves to the global, and a module's own `refs`
shadows it. The per-module import shim in the compiler and the ref hook is
removed.

The docs and news no longer point users at the private `Var._as_ref()`;
they name the public event actions instead.

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Farhan <www.mfarvirus@gmail.com>
(cherry picked from commit 381da0f)
masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
masenf pushed a commit that referenced this pull request Nov 11, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi
@masenf masenf added the release-train Issues found during agentic /prerelease-testing fanout, not necessarily validated bugs. label Nov 11, 2026
masenf added a commit that referenced this pull request Nov 12, 2026
* Materialize changelogs for reflex-base@0.11.0a1 (new-prerelease-minor)

* Materialize changelogs for reflex-components-code@0.11.0a1, reflex-components-core@0.11.0a1, reflex-components-radix@0.11.0a1 (new-prerelease-minor)

* Materialize changelogs for reflex-components-lucide@1.1.2a1, reflex-hosting-cli@0.2.2a1, reflex-otel@0.2.1a1, reflex-release@0.2.2a1 (new-prerelease-patch)

* Materialize changelogs for reflex@0.11.0a1 (new-prerelease-minor)

* Carry the train's changelog edits for fragments changed after 0.11.0a1

#7818, #7816, #7800, #7806 and #7799 edited news fragments that the
0.11.0a1 materialization had already consumed. On the release train
(r/pre-2026.11.11) those edits were folded into the matching 0.11.0a1
CHANGELOG.md entries when the fixes were cherry-picked; this carries the
same edits to main, where the fragments are consumed by the
materialization commits above.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

* Tidy the 0.11.0a1 changelog sections

Dedupe entries that appeared in both reflex and reflex-base (SetVar,
@rx.event, rx.client_state, awaitable handlers, foreach hooks, lazy
libraries, blocking detection) and in reflex-components-core (foreach over
set vars), keeping one entry in the reflex changelog. Merge entries for the
same change: deploy_url default with the CORS change, React Compiler with
auto_memoize, the reflex run shutdown and --json entries, the backend-var
errors, the db page-evaluation fixes, and the Redis cancelled-handler fixes.

Drop entries that fix features new in this alpha (blocking-monitor report,
array ref names, middleware on awaited handlers, folded into the feature) or
describe internals (stable ref names, AdminDashRemovedError), trim
implementation narrative, and order each category by user impact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ESN8DhETqtSLLtGDUeGGwV

* Tidy the pending news fragments for the next 0.11 alpha

Drop fragments that fix behavior new in 0.11.0a1 (awaitable handler
returns and hints, @rx.event stacking, the storage factory check, the
alembic env.py and page-evaluation regressions, the refs import, the
same-origin proxy check, the auto_memoize warning) and fold what users
need from them into the matching 0.11.0a1 changelog entries. Remove the
reflex-base copies of fragments duplicated in reflex, the base half of the
upload error fix (kept in components-core), the dependency-floor and
docstring fragments, and merge the two DeclarativeBase detection
fragments. Recast the reflex.model import fix as a performance entry and
trim implementation detail from the rest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ESN8DhETqtSLLtGDUeGGwV

* Materialize changelogs for reflex@0.11.0a2, reflex-base@0.11.0a2, reflex-components-core@0.11.0a2 (continued-prerelease)

* Materialize the #7855 fragment under reflex-base 0.11.0a2

#7855 (Don't wait in Thread.join(timeout) when draining supervised output)
merged to main after 0.11.0a2 was cut. It ships in 0.11.0, so its entry
goes into the 0.11.0a2 section, which release-from-prerelease collapses
into the final 0.11.0 section, and the fragment is consumed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

* Add the #7855 entry to the reflex-base 0.11.0a2 section

The previous commit consumed the fragment but left the changelog edit
unstaged; this adds the entry it was meant to carry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

* Keep main's sibling floors instead of the train's alpha floors

The alpha materializations raised the root and reflex-components-core
floors to the train's alphas (reflex-components-core >= 0.11.0a1, ...).
Those tags live on r/pre-2026.11.11 and are not reachable from main, so
main's commits build the siblings as 0.10.2.devN / 1.1.2.devN, which
check-min-deps rejects. Keep main's .dev0 floors; release-from-prerelease
lifts each to the earliest published final once that sibling is tagged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dxjadq3qkhKnqZR2b9WBFi

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

on deck PRs lined up to review / merge next release-train Issues found during agentic /prerelease-testing fanout, not necessarily validated bugs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants