chore: version packages#711
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
July 23, 2026 19:24
b91f454 to
81c0c5f
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
July 23, 2026 19:26
81c0c5f to
58904ff
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.
Releases
@vuetify/v0@1.0.1
Patch Changes
#602
e866af7Thanks @sridhar-3009! - fix(Snackbar): SnackbarPortal creates a stacking context so its z-index takes effect (#602)The teleported snackbar region applied its stack z-index to a
position: staticelement, which CSS ignores — a body-fallback snackbar could render behind positioned page chrome regardless of its z-index.SnackbarPortalnow setsposition: relativealongside the z-index (visually neutral, no offsets) so the stacking context is established.Portal'szIndexslot prop is now documented to require a positioned element.#624
64b839cThanks @sridhar-3009! - fix(Snackbar): add anurgentprop that switches the live region torole="alert"(#624)Informational snackbars keep
role="status"(a polite live region); settingurgentswitches torole="alert"(assertive) so critical notifications interrupt assistive technology instead of waiting for it to go idle (WCAG 4.1.3, Status Messages).#567
05526f0Thanks @johnleider! - fix(createTokens): a token removed via its ownticket.unregister()no longer leaves a stale value in the resolution cache (#567)resolve()results were only invalidated through the context-level mutator methods, so removing a token via its ticket's ownunregister()— which is bound to the underlying registry — left the cache stale and subsequentresolve()calls returned the removed value. Cache invalidation now runs off registry mutation events, covering every removal and update path uniformly.#566
ff9c430Thanks @johnleider! - fix(createTokens): resolve aliases reached through a segment path, return directly-passed TokenAlias literals, and cache chained resolutions (#566)resolve()now follows a{alias}that a dotted-segment lookup lands on — previously it returned the raw'{alias}'string (visible underflat: true, where nested objects are stored whole and addressed by segment). ATokenAliasobject passed directly toresolve()now returns its$value(previously a non-alias$valuewas stringified and looked up as an id, yieldingundefined), and aliased resolutions cache the outer key rather than only the terminal hop.resolve<T = unknown>()also accepts an optional return-type parameter.