Repository navigation
chore(deps): update dependency ovsx to v1 - #252
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
June 11, 2026 19:42
baa4a15 to
5795a82
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
June 27, 2026 02:55
5795a82 to
e47c7a3
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
August 2, 2026 08:59
e47c7a3 to
6d85472
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
2 times, most recently
from
August 11, 2026 23:45
ded3eae to
9cad770
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
August 26, 2026 17:59
9cad770 to
0d4d98a
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
September 10, 2026 16:32
0d4d98a to
9154905
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
2 times, most recently
from
October 5, 2026 15:23
9154905 to
db36d6d
Compare
renovate
Bot
force-pushed
the
renovate/ovsx-1.x
branch
from
October 16, 2026 17:31
db36d6d to
08a3297
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 contains the following updates:
0.10.9→1.3.0Release Notes
eclipse-openvsx/openvsx (ovsx)
v1.3.0Compare Source
Changed
publishchecks a package against the size limit that applies to its own namespace, which a size override can raise above the registry default, and refuses an oversized upload before sending it. Against a registry older than 1.3.0, which cannot report that limit, it warns against the default and publishes anyway; if a registry that should be able to report it does not answer, it says the check did not happen rather than passing silently (#2129)Fixed
--versionreads the version frompackage.jsonat runtime instead of a generatedsrc/version.ts, so it can no longer report a stale version (#2295)publishnow deletes the.vsixit packages into the temp directory once publishing finishes or fails, instead of leaving one behind per package and target (#2286)X-OpenVSX-Tokenheader, which carries the personal access token when--username/--passwordare set, on a redirect to another origin, as is done forAuthorization(#2309)<!doctype html>casing, or atext/htmlContent-Type) now fails with an error naming the status, instead of printing the raw HTML or a JSONSyntaxError(#2326)Dependencies
viteas a direct dev dependency - vitest 5 no longer bundles it, only requires it as a peer (#2291)leven; the command-suggestion distance check now uses a vendored Levenshtein implementation, the same way@vscode/vsceitself replaced its ownlevendependency in 4.0.0 (#2290)tmp; temporary file names are now generated withcrypto.randomUUID(#2284)follow-redirects; requests usenode:http/node:httpsand the registry client follows redirects itself (#2309)v1.2.0Compare Source
Added
--follow-symlinkstopublish, forwardingvsce's option of the same name so that the file walk recurses into symlinked directories instead of packing each symlink as a file. Needed for anode_modulesassembled out of symlinks, as pnpm's is (#368)searchcommand to search the registry for extensions, mirroring the web UI's search:--category,--target,--sort-byand--sort-ordernarrow the query,--sizeand--offsetpage through the results, and--jsonprints the registry's raw response (#2154)listcommand to print the extensions a namespace holds, sorted by name so the output stays stable across registries, with--jsonfor the raw namespace metadata (#2154)showcommand to print an extension's metadata, mirroringvsce show: identity, publisher, rating, notices and a version history listing each version's target platforms (#2149).namespace.extension@versionreports a single version,--targetscopes the report to one target platform,--all-versionslists every published version instead of the most recent few, and--jsonprints the registry's raw metadataunpublishcommand to delete an extension or some of its versions, mirroringvsce unpublish(#1958); requires a registry running version 1.2.0 or later, whichunpublishchecks for before deletingpublishchecks the packaged extension's size against the limit reported by the registry's/api/versionendpoint before uploading, instead of failing only after the upload completes (#1953)verifycommand to check a downloaded.vsixpackage's signature against the registry's public key, mirroringvsce verify-signature(#993)verify-signaturecommand, verifying an already-extracted package/manifest/signature file trio entirely offline (no registry involved), matchingvsce verify-signature's own command shape (#993)Fixed
Error messages naming a URL no longer include its query string, which for
createNamespace,verifyPat,publishanddeletecarried the personal access token straight to stderr and into CI logs (#2186)A connection lost after a JSON response has started no longer leaves the command waiting on a body that is not coming: the response's own error is now what settles the request, so it fails with the reset rather than hanging (#2186)
Requests now give up after 30 seconds without progress instead of hanging indefinitely when a server accepts a connection and then says nothing.
OVSX_TIMEOUToverrides the duration in milliseconds andOVSX_TIMEOUT=0disables it; it measures inactivity, so a large extension downloading slowly is unaffected, and it covers the trusted-publishing ID token request as well as the registry's own (#2186)Fix downloads that could be read before they were written.
downloadresolved when the response ended rather than when the file was closed, and a write stream opens and flushes asynchronously, so a caller reading the path immediately afterwards could find the file empty or absent - whichverifydid, intermittently failing to read the public key it had just fetched. A failed download no longer touches the target path: the body is written beside it and renamed into place only once it has arrived whole, so a 404 or a dropped connection leaves what was there alone. A connection dropped mid-download now rejects rather than leaving the caller waiting forever (#2185)Changed
createNamespace,verifyPat,publishanddeletenow send the personal access token primarily via anAuthorization: Bearerheader (or, whenOVSX_USERNAME/OVSX_PASSWORDare set, anX-OpenVSX-Tokenheader, sinceAuthorizationis then already in use for Basic auth to a fronting proxy), moving away from atokenquery parameter that gets recorded in server and reverse-proxy access logs. The CLI checks the registry's reported version (/api/version) and only still sends the token as a query parameter, alongside the header, when talking to a registry older than 1.3.0, i.e. one that predates header support - including one whose version can't be determined at all, which is treated as too old rather than assumed to be caught up; on 1.3.0 and later the header is all it sends (#1344)publish --trusted-publishingretries the token exchange when the registry answers that it could not verify the ID token (502, 503, 504), rather than failing the build on a blip reaching the identity provider. A refusal is never retriedpublish --trusted-publishingrequests a new token and retries once when the registry refuses the one it was publishing with. The issued token is short-lived and shared by every target platform of a release, so publishing a wide fan-out of large packages could outlive it and fail partway through. Targets that are refused together share one new token, and a token supplied with--patis never retriedDependencies
v1.1.1Compare Source
Dependencies
10.2.0to10.4.03.1.4to3.1.54.3.0to4.3.1v1.1.0Compare Source
Added
--allow-missing-repositoryoption to thepublishcommand, passed on tovsceto package an extension whosepackage.jsonhas norepositoryfield without asking for confirmation (#1735)publishcan exchange an OIDC ID token for a short-lived publishing token, via--trusted-publishing,--idTokenand--oidcAudienceChanged
keytarwithcross-keychainto store credentials in the system keychain (#1950)logincommand (#1966Dependencies
4.2.0to4.3.0(#1976)7.5.16to7.5.21(#1987)1.1.16to1.1.18(#2031)v1.0.2Compare Source
Dependencies
0.2.6to0.2.7(#1903)7.5.11to7.5.16(#1911)4.0.4to4.0.6(#1910)4.1.1to4.2.0(#1912)14.1.1to14.2.0(#1913)v1.0.1Compare Source
Fixes
getUrlmethod (#1893)v1.0.0Compare Source
Dependencies
3.1.0to3.1.2(#1829)5.0.5to5.0.6(#1846)6.15.0to6.15.2(#1869)0.2.4to0.2.6(#1877)v0.10.12Compare Source
Dependencies
1.15.6to1.16.0(#1759)10.1.0to10.2.0(#1820)v0.10.11Compare Source
Dependencies
2.3.1to2.3.2(#1719)4.0.3to4.0.41.1.12to1.1.13(#1725)2.0.2to2.0.35.0.4to5.0.54.17.23to4.18.1(#1745)v0.10.10Compare Source
Dependencies
6.12.6to6.14.0(#1632)8.17.1to8.18.07.5.7to7.5.11(#1681)3.1.5,9.0.9and10.2.41.13.6to1.13.8(#1656)3.3.1to3.4.2(#1703)Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.