New Release #1012
Merged
New Release #1012
Conversation
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
The extension no longer uses the `Python: Select Interpreter` mechanism for configuring Python environments, but instead relies on the `esbonio.sphinx.pythonCommand` option. Closes #984
When saving the config to the db, esbonio tried to process the `values` key that appears to have contained additional information about a configuration value - such as the scope that needs to be recalculated when its value changes. Trying to handle this introduced a strange bug #969 where configuration values that were set to a list of *exactly* 3 values would be corrupted by the sphinx agent and would crash the process. However, this `values` key was declared private and renamed to `_options` in [1]. This commit fixes the issue by ignoring this `_options` key and removing the `scope` column (which is now always empty anyway) from the database [1]: sphinx-doc/sphinx@68af0ac
updates: - [github.com/astral-sh/ruff-pre-commit: v0.8.6 → v0.11.4](astral-sh/ruff-pre-commit@v0.8.6...v0.11.4) - [github.com/pre-commit/mirrors-mypy: v1.14.1 → v1.15.0](pre-commit/mirrors-mypy@v1.14.1...v1.15.0)
for more information, see https://pre-commit.ci
Also give them the option of selecting an interpreter using the Python extension
This reverts commit 01f4838.
This should remove the iframe border, which is very noticeable when previewing a dark mode page in dark mode vscode.
This guide now depends on just vanilla nvim v0.11 and should be much easier to maintain going forward
Due to timing issues between the background sphinx build and `textDocument/diagnostic` requests from the client, the only way to provide a good experience is to issue `workspace/diagnostic/refresh` requests each time a build completes to force the client to ask for an update. Taking advantage of the better `initialize` request handling in `pygls` v2, we only register our pull-model diagnostic support when the client advertises all of the capabilities we need to provide a good experience.
syncing diagnostics on app creation has the side-effect of purging all the diagnostics that were recorded the last time the sphinx agent was used for the project. Instead, only sync the diagnostics when a build completes
This allows diagnostics recorded from the previous editing session to be provided
Where we would call `sync_diagnostics` in the push model, use the same trigger to send a refresh request to the clients that support it. This should ensure diagnostics are reported in a more timely fashion.
Bumps [@vscode/test-electron](https://github.com/Microsoft/vscode-test) from 2.4.1 to 2.5.2. - [Changelog](https://github.com/microsoft/vscode-test/blob/main/CHANGELOG.md) - [Commits](microsoft/vscode-test@v2.4.1...v2.5.2) --- updated-dependencies: - dependency-name: "@vscode/test-electron" dependency-version: 2.5.2 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.8.2 to 5.8.3. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release-publish.yml) - [Commits](microsoft/TypeScript@v5.8.2...v5.8.3) --- updated-dependencies: - dependency-name: typescript dependency-version: 5.8.3 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.2 to 0.25.5. - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.25.2...v0.25.5) --- updated-dependencies: - dependency-name: esbuild dependency-version: 0.25.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [semver](https://github.com/npm/node-semver) from 7.7.1 to 7.7.2. - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md) - [Commits](npm/node-semver@v7.7.1...v7.7.2) --- updated-dependencies: - dependency-name: semver dependency-version: 7.7.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [ovsx](https://github.com/eclipse/openvsx/tree/HEAD/cli) from 0.10.1 to 0.10.2. - [Release notes](https://github.com/eclipse/openvsx/releases) - [Changelog](https://github.com/eclipse/openvsx/blob/master/cli/CHANGELOG.md) - [Commits](https://github.com/eclipse/openvsx/commits/HEAD/cli) --- updated-dependencies: - dependency-name: ovsx dependency-version: 0.10.2 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
--- updated-dependencies: - dependency-name: "@vscode/vsce" dependency-version: 3.6.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
--- updated-dependencies: - dependency-name: "@vscode/test-cli" dependency-version: 0.0.11 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
for more information, see https://pre-commit.ci
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.
I can't believe we're three months on from the last pre-release already...