build(deps): bump socket.io-parser from 3.3.0 to 3.3.3 in /packages/cli/test/dev/fixtures/18-marko #429
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Fixes error: `Cannot read property 'spinner' of undefined`
…faces (vercel#5739) `@vercel/python` has been incorrectly "unquoting" the incoming request URL for all Python interfaces (basic, WSGI, ASGI). The proper behavior is to pass along the request URL to the serverless function handler unmodified. This is proven by the additional test that is added in this PR, which actually fires up the corresponding Python server via i.e. `python3 api/asgi.py`, and executes the test probes defined in the `test/fixtures/00-request-path/vercel.json` file. Adding this test ensures that the request URL behavior of `@vercel/python` matches the behavior as compared to executing via `python` directly.
- vercel@21.2.1-canary.0 - @vercel/python@1.2.5-canary.0
- vercel@21.2.1
Fixes these strange Windows failures that randomly started happening: https://github.com/vercel/vercel/pull/5761/checks?check_run_id=1780742477
There was an issue with `output.spinner()` spinner if the old-style interface was used (invoking the return value to stop the spinner), which caused the internal spinner instance in `output` to be defined, but in a "stopped" state. Then later the `text` gets updated to a different value but the spinner is still stopped and nothing gets rendered. The fix is to ensure that `output.stopSpinner()` is called rather than directly invoking the cancel function. In fact, the return value of `output.spinner()` has been removed completely.
- @vercel/build-utils@2.8.1-canary.0 - @vercel/cgi@1.0.7-canary.0 - vercel@21.2.2-canary.0 - @vercel/client@9.0.6-canary.3 - @vercel/go@1.1.8-canary.0 - @vercel/node@1.9.1-canary.0 - @vercel/python@1.2.5-canary.1 - @vercel/ruby@1.2.6-canary.0
Both `vc` and `vc dev` already ask to link/setup when the project is not found, so this will update the error message to mention the possible reasons why a project was not found. ### Before ``` $ vc Vercel CLI 21.2.1 ❗️ Your project was either removed from Vercel or you’re not a member of it anymore. ? Set up and deploy “~/Code/myproject”? [Y/n] ``` ### After ``` $ vc Vercel CLI 21.2.1 ❗️ Your Project was either deleted, transferred to a new Team, or you don’t have access to it anymore. ? Set up and deploy “~/Code/myproject”? [Y/n] ``` ### 📋 Checklist #### Tests - [x] The code changed/added as part of this PR has been covered with tests - [x] All tests pass locally with `yarn test-unit` #### Code Review - [x] This PR has a concise title and thorough description useful to a reviewer - [x] Issue from task tracker has a link to this PR
- vercel@21.2.2-canary.1
- vercel@21.2.2 - @vercel/go@1.1.8
…#5761) ### Related Related to vercel#4754 ### Upstream https://aws.amazon.com/blogs/compute/node-js-14-x-runtime-now-available-in-aws-lambda/ ### 📋 Checklist #### Tests - [x] The code changed/added as part of this PR has been covered with tests - [x] All tests pass locally with `yarn test-unit` #### Code Review - [x] This PR has a concise title and thorough description useful to a reviewer - [x] Issue from task tracker has a link to this PR
- @vercel/build-utils@2.8.1-canary.1 - vercel@21.2.3-canary.0 - @vercel/client@9.0.6-canary.4
- @vercel/build-utils@2.9.0 - vercel@21.2.3 - @vercel/client@9.0.6
The version of `sharp` used in gridsome 0.6.0 does not compile on Node 14.
This PR converts the `frameworks.json` file to TypeScript, and extends the values with the detection logic from `@vercel/static-build`, so that it's publicly editable. You also don't need to do the type casting downstream anymore. As a consequence, it also makes Zola a 1st-class framework, as it was previously missing from the `frameworks.json` file, but present in the static-build frameworks. An example has been included based on their "Getting Started" tutorial. CH-3808 CH-18771
- @vercel/frameworks@0.2.1-canary.0 - @vercel/build-utils@2.9.1-canary.0 - vercel@21.2.4-canary.0 - @vercel/client@9.0.7-canary.0
This PR adds a boolean `user` property to help determine which routes where added by the user and which routes were added by the platform.
Fixes unit test failures like: https://github.com/vercel/vercel/runs/1867209532#step:11:191 from PR vercel#5740
This will be necessary for static type analysis in our API docs generator. The default export is still typed as `Framework[]` for backwards-compat purposes, but the `frameworks` export is the statically typed array.
…l deployments (vercel#5818) All demo URLs must be public for the template import flow, so this test case ensures that we don't accidentally publish a demo URL that is not public.
* [frameworks] Add type annotations This will be necessary for static type analysis in our API docs generator. * Apply suggestions from code review Co-authored-by: Steven <steven@ceriously.com> * Add quotes to @examples Co-authored-by: Steven <steven@ceriously.com>
- @vercel/frameworks@0.2.1-canary.1 - @vercel/build-utils@2.9.1-canary.1 - vercel@21.2.4-canary.1 - @vercel/client@9.0.7-canary.1 - @vercel/routing-utils@1.9.3-canary.0
This PR improves the CLI in a way that if the API from any request returns a response which contains a header with the prefix `x-vercel-warning-*`, `x-vercel-notice-*` or `x-vercel-tip-*`, it will print out the message to the output to let the user know. This new feature also supports additional headers which improve the message, so that a link can be printed out for more information. Those are `x-vercel-link-*`, where we specify a link, and `x-vercel-action`, where we specify the text before the link. Here's an example for a warning message which warns the user if they add a DNS record for a domain which does not use Vercel Nameservers: <img width="719" alt="Screenshot 2021-01-18 at 17 49 14" src="https://user-images.githubusercontent.com/35507539/104943788-8da12400-59b6-11eb-8e54-77a3c517e56d.png"> The API request from above which creates a DNS record has the following HTTP response headers set: ``` x-vercel-warning-create-domain-record: Your Domain isn't using Vercel nameservers. In order for the changes to your DNS Records to get applied, however, it needs to. x-vercel-link-create-domain-record: https://vercel.link/configure-vercel-nameservers ``` If `x-vercel-action` is not specified, it defaults to `Learn More`. ### 📋 Checklist <!-- Please keep your PR as a Draft until the checklist is complete --> #### Tests - [ ] The code changed/added as part of this PR has been covered with tests - [x] All tests pass locally with `yarn test-unit` #### Code Review - [x] This PR has a concise title and thorough description useful to a reviewer - [x] Issue from task tracker has a link to this PR
- vercel@21.2.4-canary.2
…ercel#5829) Fixes TypeScript error: ``` test/unit.framework-detector.test.ts:52:40 - error TS4104: The type 'readonly Framework[]' is 'readonly' and cannot be assigned to the mutable type 'Framework[]'. 52 expect(await detectFramework({ fs, frameworkList })).toBe(null); ~~~~~~~~~~~~~ ```
Seems like this might help with the networking issues in CI. See yarnpkg/yarn#4890 (comment)
This reverts commit 356739e.
…76c8078 [Snyk] Security upgrade next from 9.2.2 to 9.5.3
…cli/test/dev/fixtures/02-angular-node/elliptic-6.5.4 fix: Dependabot/npm_and_yarn/packages/cli/test/dev/fixtures/02_angular_node/elliptic_6.5.4
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-POSTCSS-1090595 - https://snyk.io/vuln/SNYK-JS-POSTCSS-1255640
Bumps [qs](https://github.com/ljharb/qs) from 6.5.2 to 6.5.3. - [Release notes](https://github.com/ljharb/qs/releases) - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.5.2...v6.5.3) --- updated-dependencies: - dependency-name: qs dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…angular/qs-6.5.3 build(deps): bump qs from 6.5.2 to 6.5.3 in /examples/angular
Bumps [moment-timezone](https://github.com/moment/moment-timezone) from 0.5.33 to 0.5.40. - [Release notes](https://github.com/moment/moment-timezone/releases) - [Changelog](https://github.com/moment/moment-timezone/blob/develop/changelog.md) - [Commits](moment/moment-timezone@0.5.33...0.5.40) --- updated-dependencies: - dependency-name: moment-timezone dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [moment-timezone](https://github.com/moment/moment-timezone) from 0.5.33 to 0.5.40. - [Release notes](https://github.com/moment/moment-timezone/releases) - [Changelog](https://github.com/moment/moment-timezone/blob/develop/changelog.md) - [Commits](moment/moment-timezone@0.5.33...0.5.40) --- updated-dependencies: - dependency-name: moment-timezone dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. - [Release notes](https://github.com/SamVerschueren/decode-uri-component/releases) - [Commits](SamVerschueren/decode-uri-component@v0.2.0...v0.2.2) --- updated-dependencies: - dependency-name: decode-uri-component dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
…code-uri-component-0.2.2
…nuxtjs/decode-uri-component-0.2.2 build(deps): bump decode-uri-component from 0.2.0 to 0.2.2 in /examples/nuxtjs
…nt-timezone-0.5.40
…hexo/moment-timezone-0.5.40 build(deps): bump moment-timezone from 0.5.33 to 0.5.40 in /examples/hexo
…dev/fixtures/07-hexo-node/moment-timezone-0.5.40
…cli/test/dev/fixtures/07-hexo-node/moment-timezone-0.5.40 build(deps): bump moment-timezone from 0.5.33 to 0.5.40 in /packages/cli/test/dev/fixtures/07-hexo-node
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) from 3.3.0 to 3.3.3. - [Release notes](https://github.com/socketio/socket.io-parser/releases) - [Changelog](https://github.com/socketio/socket.io-parser/blob/main/CHANGELOG.md) - [Commits](socketio/socket.io-parser@3.3.0...3.3.3) --- updated-dependencies: - dependency-name: socket.io-parser dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
added 2 commits
December 18, 2022 11:01
Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
…dev/fixtures/18-marko/socket.io-parser-3.3.3 Signed-off-by: Jacquelyn Vinson <jacqvinson@gmail.com>
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
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.
Bumps socket.io-parser from 3.3.0 to 3.3.3.
Release notes
Sourced from socket.io-parser's releases.
Changelog
Sourced from socket.io-parser's changelog.
... (truncated)
Commits
cd11e38chore(release): 3.3.3fb21e42fix: check the format of the index of each attachment3b0a392chore(release): 3.3.289197a0fix: prevent DoS (OOM) via massive packets (#95)25ca624chore(release): 3.3.1b51b39btest: use Node.js 10 for the browser tests4184e46chore: bump component-emitter dependencyDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.