Repository navigation
Update dependency ovsx to v1.4.0 - #44
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
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:
1.3.0→1.4.0Used by
vscode-extension-publish.ymlonly; nothing here runs it before a release. Before merging: read the changelogs of vsce and ovsx (publish --packagePath,--skip-duplicate); check theirengines.nodeagainstnode-version. After merging: Move major tag, and watch the next extension release (vscode-jest-runner).Release Notes
eclipse-openvsx/openvsx (ovsx)
v1.4.0Compare Source
Added
publish --registrationCode(orOVSX_REGISTRATION_CODE) completes the trusted publisher registration of a private repository on its first publish (#2350)Fixed
publish -i ext.vsixnow warns about the packaging options it ignores, aspublish ext.vsixdoes, naming the file, and publishes the package once instead of once per--target(#2351)getandverifyignore a timeout or connection reset while draining the error body of a rejected download, instead of cleaning up a partial file that was never written (#2386)publishprints the exact byte counts next to the friendly sizes of a size limit, so a package one byte over its limit no longer reads as "1 MB exceeds the size limit of 1 MB" (#2392)publish --trusted-publishingasks the registry which audience its ID token must carry, so trusted publishing works on a registry whose configured audience is not its URL (#2391)publish --trusted-publishingonly sends its ID token to a registry reached over https, apart from a loopback address, and a failed registry version lookup is no longer remembered (#2391)searchreports an invalid--sizeor--offsetvalue as a usage error instead of crashing with a stack trace (#2414)verify-pat,unpublishandcreate-namespaceonly store a prompted personal access token once the registry accepts it, so a mistyped token is no longer reused on every later run untillogout(#2427)Removed
LoginOptionsis no longer exported from the package entry point; it was the options type oflogin, which the entry point never actually exportedDependencies
is-ciwithci-info4.4.0 (#2377)@azure/msal-nodeto 7.1.1 (#2388)yarnfrom 4.9.1 to 4.18.1 and setnpmMinimalAgeGateto 7 days, so versions published in the last 7 days are not picked for new resolutions (#2393)Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.