docs: fix explicit env vars docs version#15968
Merged
Rich-Harris merged 3 commits intoJun 7, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: 3995c50 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This was referenced Jun 7, 2026
Merged
Rich-Harris
pushed a commit
that referenced
this pull request
Jun 8, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## @sveltejs/kit@2.63.1 ### Patch Changes - fix: use SSE for `query.live` ([#15957](#15957)) - fix: use forward slashes in the generated `env.d.ts` import path on Windows ([#15977](#15977)) - fix: allow `$app/environment` with a warning when `explicitEnvironmentVariables` is enabled ([#15980](#15980)) - fix: avoid importing Vite while validating explicit environment variables ([#15953](#15953)) - docs: adjust the release version of explicit env vars ([#15968](#15968)) - fix: ensure `version` is defined when importing from `$app/env` with explicit environment variables ([#15971](#15971)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
teemingc
reviewed
Jun 8, 2026
| '@sveltejs/kit': patch | ||
| --- | ||
|
|
||
| docs: adjust the release version of explicit env vars |
Member
There was a problem hiding this comment.
Note that I don’t think we need a changeset for doc changes in the future
Contributor
Author
There was a problem hiding this comment.
I wasn’t sure as I changed parts of the package
Noted!
Member
There was a problem hiding this comment.
Yeah, I used to think the same. I think we omit it if it there are no new changes to how the user interacts with the framework or how their app runs.
Rich-Harris
pushed a commit
that referenced
this pull request
Jun 8, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 version-3, this PR will be updated.⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ `version-3` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `version-3`.⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ # Releases ## @sveltejs/kit@3.0.0-next.2 ### Patch Changes - fix: use SSE for `query.live` ([#15957](#15957)) - fix: use forward slashes in the generated `env.d.ts` import path on Windows ([#15977](#15977)) - fix: avoid importing Vite while validating explicit environment variables ([#15953](#15953)) - docs: adjust the release version of explicit env vars ([#15968](#15968)) - fix: ensure `version` is defined when importing from `$app/env` with explicit environment variables ([#15971](#15971)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
#15934 was created before Kit 2.62 got released, thus its docs updates naturally indicated 2.62 as a target version. However, 2.62 got released before merging this PR (or not including it). As a result, the "since version" is erroneous.
This PR fixes this by bumping the numbers everywhere the original PR set them to 2.63, which actually includes the change.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm testand lint the project withpnpm lintandpnpm checkChangesets
pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.Edits