chore: release Fronts packages (next) - #176
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
4 times, most recently
from
July 25, 2026 12:55
faa212c to
0a1bad7
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
July 25, 2026 13:00
0a1bad7 to
879b2fb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
masteris currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmaster.Releases
@fronts/[email protected]
Major Changes
FRONTS_APP_PROTOCOL_VERSIONandFRONTS_IFRAME_PROTOCOL_VERSIONare now1, and the branded application symbols move from@fronts/core/application/v2to@fronts/core/application/v1. A producer built against the previous prerelease constants no longer validates, which is intentional while nothing is published.Minor Changes
createModuleHost(), a@fronts/corecomposition shortcut for applications the caller can already import. Anappsmap of module loaders synthesizes the static resolver and application loader that previously had to be written by hand, so a shell that needs no runtime deployment policy reaches a typedHostCompositionwithout a transport package. Props contracts are inferred from each application's owndefineAppdeclaration, and every Host behaviour below the composition root is unchanged.HostComposition, application contract, name, and catalog types so delivery and framework packages can share typed application references without depending on one another.runtime resources could not be released completely.
Patch Changes
violations remain visible to host audits.
validated.
deployment envelopes before exposing them to runtime extensions.
inline event handlers.
HostCompositioncontracts invariant so compositions with the same application names but different props cannot be rebound accidentally.capability requirements for ordinary applications and the real child application.
provider result as incomplete host cleanup.
or retaining transferred message ports.
cannot widen to
undefined.asynchronous resolution begins.
protocol and host, Module Federation 2 adapter, React and Vue 3 adapters, isolation containers,
production replacement controls, observability, and examples.
errors.
host lifecycle.
application.
their matching resolve or load phase.
remote applications.
the runtime as idle.
@fronts/[email protected]
Minor Changes
createMfHost()deployments to carry resolved metadata for container resolvers, policy, and observability.createMfHost()as a typed composition shortcut over the official Module Federation runtime, static or caller-supplied resolution, the existing MF adapter, andcreateFrontsHost(). Its result carries the application reference catalog required by framework bindings, including non-default exposes.Patch Changes
composition cannot leave an unreachable instance in the official runtime registry.
load or preload when registration cancels the operation.
normalization cannot rewrite resolved deployment data.
state cannot become trusted remote, selector, preload, or deployment metadata configuration.
protocol and host, Module Federation 2 adapter, React and Vue 3 adapters, isolation containers,
production replacement controls, observability, and examples.
branching and preload logic.
Module Federation Host is created instead of deferring malformed configuration to first resolve.
@fronts/[email protected]
Minor Changes
createReactBindings()for rendering any typed Host composition through an inlineApp, stable application component factories, and typed preloading. Bindings infer application contracts and reference defaults fromcreateMfHost()results while remaining transport-neutral.retry()fromuseRemoteApp()and pass{ error, retry }to theRemoteAppfallback so a host can recover from a failed resolve, load, or mount without remounting its own React tree. The fallback now receives a failure object rather than a bareError.Patch Changes
update(), and acceptarePropsEqualfor callers that need a different equality contract. This matches the value-based comparison the Vue adapter already performed.@fronts/mfand official runtime dependencies required by the typed ModuleFederation Host examples.
preload inputs cannot replace catalog names or exposes or inject detached Host operation controls.
blocking lifecycle teardown.
Vue cannot silently consume fields before they reach the remote application. Inline
Appbindingscontinue to support those contracts through their nested
propsobject.returned.
host hook.
useRemoteAppso an inline object literal re-created by an ordinary render no longer unmounts and remounts the application. Container request resolvers and other functions still compare by reference.protocol and host, Module Federation 2 adapter, React and Vue 3 adapters, isolation containers,
production replacement controls, observability, and examples.
@fronts/[email protected]
Minor Changes
createVueBindings()for rendering any typed Host composition through an inlineApp, stable application component factories, and typed preloading. Bindings infer application contracts and reference defaults fromcreateMfHost()results while remaining transport-neutral.retry()from the VueuseRemoteApp()composable and pass{ error, retry }to theRemoteApperrorslot andfallbackprop so a host can recover from a failed resolve, load, or mount without recreating its own component tree. Both now receive a failure object rather than a bareError.Patch Changes
RemoteAppcontainerprop against the built-in container requests sotagName,className,attributes,mode, anddelegatesFocusare accepted. The prop previously resolved to the bareContainerRequestbase, whose only member istype, so excess property checking rejected every documented DOM and Shadow DOM request.update(), and acceptarePropsEqualfor callers that need a different equality contract. In-place mutation of a reactive prop object still updates the application.@fronts/mfand official runtime dependencies required by the typed ModuleFederation Host examples.
arePropsEqualoption on the VueRemoteAppcomponent and forward it to the host composable.preload inputs cannot replace catalog names or exposes or inject detached Host operation controls.
Vue cannot silently consume fields before they reach the remote application. Inline
Appbindingscontinue to support those contracts through their nested
propsobject.composable.
useRemoteApp()watcher so an inline object literal re-created by an ordinary render no longer unmounts and remounts the application. Container request resolvers and other functions still compare by reference.protocol and host, Module Federation 2 adapter, React and Vue 3 adapters, isolation containers,
production replacement controls, observability, and examples.