Repository navigation
chore: update versions - #9
Merged
Merged
Conversation
vland-bot
Bot
force-pushed
the
changeset-release/main
branch
from
October 13, 2026 01:16
ba5fbe4 to
7f7e7f6
Compare
vland-bot
Bot
force-pushed
the
changeset-release/main
branch
from
October 13, 2026 03:55
7f7e7f6 to
64fc14d
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 main, this PR will be updated.
Releases
@variablelab/theme-toggle@2.0.0Major Changes
#8
48299eeThanks @rqbazan! - Renamed from@vlandoss/theme-toggle. The package now lives at withvariablelab/theme-toggle;@vlandoss/theme-togglewill not receive further releases.Breaking changes
@variablelab/theme-toggleinstead of@vlandoss/theme-toggle(the inline script moves tohttps://unpkg.com/@variablelab/theme-toggle/dist/initial.js).localStoragekey is now@variablelab/theme-toggle.colorMode(was@vlandoss/theme-toggle.colorMode).@variablelab/theme-toggle.colorModeChange(was@vlandoss/theme-toggle.colorModeChange). Update anydocument.addEventListener(...)listeners, or read the name fromwindow.__COLOR_MODE__.CUSTOM_EVENT.Automatic migration
Users keep their saved color mode. On init, both the inline script and
useColorModecheck for the 1.x key: if@variablelab/theme-toggle.colorModeis absent and@vlandoss/theme-toggle.colorModeexists, its value is copied to the new key. A value already stored under the new key always wins. Either way, the old key is removed.