build(deps): bump elliptic from 6.5.2 to 6.5.3 #1171
Closed
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}
* Add development note to README * Use cli as main intern UI * Unit tests pass in node * Simplify lint script
* Get test script working * Fix broken functional tests * Update showConfig unit test * Move web resources to pkg root, rebuild api data * Remove extra slash from import path in ProxiedSession
- Handle args with spaces - Change --no-instrument to --no-coverage
- Switch to eslint, update code to fix linter errors - Switch to husky and enable pre-commit linting
* Run tests using a test build of Intern * Build unit tests with webpack * Implement a new new mocking system based on rewiremock (https://github.com/theKashey/rewiremock) that works in both Node and the browser (in webpack). * Don't hide skipped and passing tests * SeleniumTunnel test updates * Use modern chromedriver * Run Selenium on non-standard port * Catch errors in finalError middleware (the middleware function signature must include a `next` parameter for Express to realize it can handle errors) * Update the test script to build browser tests when necessary * Temporarily disable some broken functional tests * Update the ci and wd test configs in `intern.json` to work with webpack-based unit tests
It was still using the old CLI syntax [ci skip]
Make devpack and ci scripts work again
- Switch to execa for running processes -- it's a bit cleaner and provides some nice cancellation functionality - Remove the lint script and just call eslint directly - Remove the preci script -- the test script handles any necesssary building - Fix the "ci" script in package.json
- Disable the brokenWindowSwitch test in IE (it hangs) - Build browser tests as ES5 - Make loader scripts and RemoteSuite configuration script IE-friendly - Add descriptive comments to tsconfig files - Make webpack paths more Windows-friendly - Make execute scripts IE-compatible - Add a mouse click listener to one of the functional test pages to visualize click locations - Add a pathRe function to create platform-compatible path-based regular expressions references #1043 references #1037
- Re-enable resolveEnvironments and Coverage reporter tests - Normalize versions at the end of the resolution process in resolveEnvironments rather than the beginning to simplify internal logic - Update resolveEnvironments tests to handle both version and browserVersion being in the resolved environments resolves #1058 references #1013
When a dev or CI test run fails, don't display the error content -- it was already displayed by Intern. resolves #1049
The Coverage tests were being run in CI, but still not locally. references #1058
Restore it when Safari compatibility has been fixed. references #1060
keepAlive allows Intern to re-use TCP connections, which can greatly speed up functional tests. references #1057
Resolve the remote environments (resolving aliases, normalizing environment descriptors) in resolveConfig. Defer parameter aliasing (e.g., ensuring both browser and browserName are present) until after environment resolution so we don't accidentally create too many environment permutations. resolves #1065 resolves #1063
Also don't add `browser` key when resolving environments. references #1064
- `intern` runs the TS intern directly (without needing to build) - `watch` starts a build watcher [ci skip]
Use a structural test rather than instanceof to check if an object is a Suite. It's possible for multiple copies of the Suite class to be loaded at once, such as when directly importing an interface or the Suite class in tests. That will cause an instanceof check to fail, even when a suite object is effectively a Suite.
The `benchmarkConfig` option wasn't handled by processOption.
Adds deepEqualExclude assertion
- Consolidate config logic into src/core/lib/config
- Move side effects and non-configuration code out of _resolveConfig in
executors
- Break config functionality down into simpler, composable parts
- Add `Configurator` class -- this class encapsulates an
environment-specific (Node or browser) config handler
- Add new error classes for config loading errors
- Remove the Config-based generic parameter from Executor
- Deprecate `help` config property
- Remove `showConfig` handling from Executor and deprecate the `showConfig`
config property. This is now handled by the UI.
- Add a `describe` command to the CLI and deprecate the `showConfigs` config
property
- All config defaults are now set in the Executor constructor
- Move Selenium typings to a standalone module so they can be used in
common config code
- Don't duplicate _rootSuite setup in Node executor
- Update config unit tests
- Test updated API
- Extensive typing updates to config and tunnel tests
- Add tests to more fully exercise config logic, including various
merging behaviors
- Replace mock classes in config and Node executor tests with real classes
using mocked dependencies
- Add new deepEqualExcludes chai assertion
- Update config docs
- Update commander dependency
references #1109
BREAKING CHANGE: Executor no longer implicitly handles the full config
process (command line args, env vars, etc.). The user will need to
manage more of Intern's configuration when using it programmatically.
BREAKING CHANGE: No config properties, aside from `configs`, are
implicitly merged. For example, `capabilities` in a config file will no
longer be implicitly merged with the default (use `capabilities+` to
retain the default).
When deciding whether to rebuild testIntern, consider HTML assets. [ci skip]
During integration tests, Sauce's Selenium relay should run on a different port than the active test tunnel.
The source and target arguments of deepMixin were incorrect in some usages.
The useLoader property of plugins wasn't being used, so plugins were being loaded twice.
The known capabilities for Safari 13+ weren't being applied. The `isValidVersion` check was checking for exactly v13 instead of 13.x.
The Command tests were using an implicit timeout of 0, which causes problems with at least Safari 13.
Bumps [jquery](https://github.com/jquery/jquery) from 3.4.1 to 3.5.1. - [Release notes](https://github.com/jquery/jquery/releases) - [Commits](jquery/jquery@3.4.1...3.5.1) Signed-off-by: dependabot[bot] <support@github.com>
An async factory function could be provided to the tdd/bdd suite registration functions (`suite` and `describe`). This was not supported, and would cause runtime errors. This is now detected at compile time and runtime. resolves #1148
SCSS is more widely used, and also doesn't generate node warnings when building. [ci skip]
Verify that the driver versions specified in webdrivers.json are downloaded during the Selenium integration test.
- `webdriver` script is a helper for updating webdrivers.json - `ghpages` script publishes webdrivers.json and Intern's schemas to a versioned directory in Intern's gh-pages branch [ci skip]
Try to download updated webdriver data from theintern.io when starting the SeleniumTunnel.
- Move showConfig handling to cli/lib/util - Support debug, showConfig, socketPort for `serve` command [ci skip]
When a WD update succeeds, cache the downloaded data file. Use this in the future if a WD download fails.
Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.2 to 6.5.3. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.5.2...v6.5.3) Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
|
|
Looks like elliptic is no longer a dependency, so this is no longer needed. |
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 elliptic from 6.5.2 to 6.5.3.
Commits
86478036.5.3856fe4dsignature: prevent malleability and overflowsDependabot 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.