Bump pyspellchecker from 0.6.2 to 0.6.3 in /.circleci#3
Conversation
Bumps [pyspellchecker](https://github.com/barrust/pyspellchecker) from 0.6.2 to 0.6.3. - [Release notes](https://github.com/barrust/pyspellchecker/releases) - [Changelog](https://github.com/barrust/pyspellchecker/blob/master/CHANGELOG.md) - [Commits](barrust/pyspellchecker@v0.6.2...v0.6.3) --- updated-dependencies: - dependency-name: pyspellchecker dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
* Automox Content Pack for XSOAR (#1) * IN-104 Implemented commands related to Administration and Vulnerability Sync use cases. * [IN-149] Adding Vulnerability Upload Playbook (#2) Added playbook to automate report uploads * [IN-152] Automox XSOAR Documentation (#3) Added documentation for Playbook, Integration, and Pack * IN-166 Automox XSOAR Unit Tests (#4) * Adding unit tests * Reviewed checklist for XSOAR submission * Cleaning up integration test files * Fixed validation issues with playbook * Updated README and Integration yaml to be consistent with args in Python. Fixed issues with fromversion and tests in Integration yaml. * Playbook documentation updates regarding supported csv formats * Present errors in a pleasant and readable way. Handled basic http fail codes * Updated delete commands to update objects in the context with deleted key * Removed test playbook from integration yaml Co-authored-by: MLainer1 <93524335+MLainer1@users.noreply.github.com> * Added Automox integration instrumentation * Fixed docker image version and schema validation in integration yaml Co-authored-by: MLainer1 <93524335+MLainer1@users.noreply.github.com> Co-authored-by: Jack Miller <94870866+ax-jmiller@users.noreply.github.com> Co-authored-by: MLainer1 <93524335+MLainer1@users.noreply.github.com>
) * Added new files: - MSDE playbooks for isolation and unisolations - new images of all playbooks - README files Modified: - Common playbooks for isolation and unisolation * . * Update RN * Changes on the PB for dealing with incorrect Device IDs * Changes on the PB - adding support for Hostname and IP * Updated RN * Fixed Issue with Task #3 in the Unisolate (filters were incorrect). * Additional fix - added else on task 26 * Applied PR comments * Applied PR comments * Applied PR comments * Updated RN for MSDE pack * Fixed issues with validation * Changed "devices" --> "device" * Added !endpoint instead the enrichment that was done through the native MSDE commands * Fixed conflicts + Updated RN * Fix Format issues * Fix RN issues * Fix dependencies * Fix dependencies * Updated RN * Updated RN * Merge from master + Resolve conflicts + Resolve comments * Updated RN * Update playbook-Isolate_Endpoint_-_Generic_V2.yml Doc review complete for this file, updated descriptions. * Update playbook-Isolate_Endpoint_-_Generic_V2_README.md doc review complete for this file. Updated descriptions to align with the yaml file. * Update playbook-Isolate_Endpoint_-_Generic_V2.yml minor additional update * Update playbook-Unisolate_Endpoint_-_Generic.yml Doc review complete for this file, updated descriptions. * Update playbook-Unisolate_Endpoint_-_Generic_README.md Doc review complete for this file, aligned the descriptions with the yaml file. * Update 2_2_0.md Doc review complete for this file, minor formatting updates. * Update playbook-Microsoft_Defender_For_Endpoint_-_Isolate_Endpoint.yml Doc review complete for the playbook-Microsoft_Defender_For_Endpoint_-_Isolate_Endpoint.yml file. @ssokolovich please confirm the following: - Lines 314, 368, 591, 645, 695 - the description for **Set Active Device** , **Set Non-valid Devices**, **Set Incorrect ID**, **Set Incorrect IP**, **Set Incorrect Hostname** is "Set a value in context under the key you entered. If no value is entered, the script doesn't do anything. This automation runs using the default Limited User role, unless you explicitly change the permissions. For more information, see the section about permissions here: https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-2/cortex-xsoar-admin/playbooks/automations.html" This description is generic - should there be descriptions specific to these tasks? - Line 500 - the description for **Check if there is any provided incorrect info** is "Check if there are any incorrect device IDs." - is this correct (incorrect info = incorrect device ID)? - Line 903 - the description for **Was any data provided?** is "'Validate/Enrich inputs through !endpoint'" - this looks like a boolean task. Is it that if it returns yes, then the playbook returns the data? * Update playbook-Microsoft_Defender_For_Endpoint_-_Unisolate_Endpoint.yml Doc review complete for the playbook-Microsoft_Defender_For_Endpoint_-_Unisolate_Endpoint.yml file. @ssokolovich - please confirm the following: - Lines 278, 333, 501, 551, 605 - the description for **Set Unisolate list**, **Set Inactive Device list**, **Set Incorrect IP**, **Set Incorrect Hostname**, **Set Incorrect ID** is generic, should it be more specific? - Line 399 - the simple description for **Print those that can't be unisolated as are not active** is "The following devices can't be isolated...." - shouldn't it be "The following devices can't be unisolated..."? - Line 659 - the description for **Check if there is any provided incorrect info** is "Check if there are any incorrect device IDs." - is incorrect info = incorrect device ID? - Line 904 - the description for **Was any data provided?** is "'Validate/Enrich inputs through !endpoint'" - is this description correct? * Update 1_6_2.md doc review complete for this file. Minor formatting update * Update 1_6_3.md doc review complete for this file, minor formatting update * Update 1_6_2.md additional minor update * Update 1_7_0.md doc review complete for this file, aligned descriptions with the yaml files. * Update RN * Update Yml description * Update Yml description Co-authored-by: julieschwartz18 <91824591+julieschwartz18@users.noreply.github.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 |
6 similar comments
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
Bumps pyspellchecker from 0.6.2 to 0.6.3.
Release notes
Sourced from pyspellchecker's releases.
Changelog
Sourced from pyspellchecker's changelog.
Commits
7b5f109update word_probability deprication warning43a2284another docstring formatbd303adformatting changes0264627Feature/typing (#113)e027a20Merge branch 'master' of https://github.com/barrust/pyspellcheckerb0f110eupdate english to removeciewordsa201cbbUpdate CHANGELOG.mdea61349add available languages classmethod (#111)876a30aUpdate README.rstDependabot 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)