f4c37985eb
chore(deps): update dependency eslint to v8.42.0
2023-06-03 09:01:42 +00:00
78c6794253
fix(doctor): update dependency appium-adb to v9.11.5
2023-06-02 13:33:41 +00:00
c416a86120
chore(appium): fix arg parser test (temp fix) ( #18718 )
2023-06-01 11:17:13 -07:00
38f86900da
fix: Do not use additional checks on opencv objects ( #18714 )
2023-06-01 06:31:30 +02:00
40fc097eda
chore(ci): avoid build on macos 14.x due to unexplained failures
2023-05-31 14:17:09 -07:00
0097c8e52e
chore(support): fix fs.walkdir test for win compat
2023-05-31 14:17:09 -07:00
1ccf857a4b
fix(strongbox): do not force-lowercase slugged containers
2023-05-31 14:17:09 -07:00
c34f2eb897
chore: use glob mode w/ rimraf
2023-05-31 14:17:09 -07:00
1d7c58ff26
chore: fix/skip tests on windows
2023-05-31 14:17:09 -07:00
d78ca63e60
chore(strongbox): tests do not assume posix paths
2023-05-31 14:17:09 -07:00
4f171ee92f
ci: add windows and macos to ci matrix
2023-05-31 14:17:09 -07:00
fd2c72fd88
fix(types): fix broken appium config schema types, temporarily
...
This appears to be a bug in `json-schema-to-typescript`, where the `ipv6` type converts to `{[key: string]: unknown}` instead of `string`.
For now, we need to drop all formatting requirements from the `address` prop until this is fixed.
This did not break CI because the `build` script of `@appium/types` was run either _after_ building the rest of the project, or not at all, and the resulting change to `appium-config.ts` was not committed.
2023-05-31 14:02:28 -07:00
3bf406015e
fix(universal-xml-plugin): update dependency @xmldom/xmldom to v0.8.8
2023-05-31 12:15:12 +00:00
56499eb997
fix(types): update dependency type-fest to v3.11.1
2023-05-31 09:01:09 +00:00
bd10bffec4
chore(docutils): update dependency mkdocs-material to v9.1.15
2023-05-30 13:02:24 +00:00
b1ee41cfc7
chore(deps): update commitlint monorepo to v17.6.5
2023-05-30 10:54:49 +00:00
cc7f5f4a52
chore(deps): update eslint-related packages to v5.59.8
2023-05-30 09:05:58 +00:00
a98d9c33c7
fix(appium): update dependency winston to v3.9.0
2023-05-27 16:32:08 +00:00
1a2260bb15
fix(docutils): update dependency yaml to v2.3.1
2023-05-27 12:35:19 +00:00
4c52fdf1d0
chore(deps): update dependency @types/node to v18.16.16
2023-05-27 09:34:42 +00:00
a959eec9cf
docs(appium): Add contributing documentation ( #18691 )
2023-05-26 22:57:01 -07:00
e96724077e
fix(schema): update definitelytyped
2023-05-26 10:39:52 +00:00
dfae94e7f3
ci: Remove v14 from the test matrix and add v20 ( #18679 )
2023-05-25 22:46:03 +02:00
0497090a90
fix(images-plugin): Make sure the template is always a buffer ( #18696 )
2023-05-25 19:16:03 +02:00
19277f6e14
fix(types): update dependency type-fest to v3.11.0
2023-05-25 09:05:01 +00:00
39a59c8bb3
chore(deps): update dependency json-schema-to-typescript to v13
2023-05-24 14:27:42 -07:00
2766dcca4c
feat(docutils): init: scafffold package.json
...
This makes `appium-docs init` add a needed prop (`typedoc.entryPoint`) to `package.json` of an extension. It will write to `package.json` _by default_, even if it exists--which is different than the default behavior of other scaffolding tasks.
Note that `appium-docs init` will now _fail_ if `--entry-point <some-file>` (or `-e`) is not provided; there's no way for us to guess what it is (this is the _source_ entry point; not necessarily the `main` file). I guess that's technically breaking, but `appium-docs init` should not be part of anyone's workflow.
2023-05-24 14:26:07 -07:00
f5b112bcca
docs(appium): fix weird sentence
2023-05-24 13:15:56 -07:00
5d6458b611
Update packages/appium/docs/en/ecosystem/build-docs.md
...
Co-authored-by: Jonathan Lipps <jlipps@gmail.com >
2023-05-24 13:15:56 -07:00
d47c805468
docs(appium): update build-docs.md
2023-05-24 13:15:56 -07:00
4c61d533b8
fix(test-support): update dependency sinon to v15.1.0
2023-05-24 13:51:21 +00:00
325d237207
fix(docutils): update dependency yaml to v2.3.0
2023-05-24 10:47:01 +00:00
8f63dabb5d
feat(appium): Allow to provide ipv6 addresses and handle broadcast addresses in logs ( #18674 )
2023-05-24 08:26:10 +02:00
5a555090c5
fix(support): update dependency semver to v7.5.1
2023-05-23 14:20:57 +00:00
81ed72f19d
chore(deps): update eslint-related packages to v5.59.7
2023-05-23 11:07:31 +00:00
f34c75c650
fix(doctor): update dependency appium-adb to v9.11.4
2023-05-22 13:47:30 +00:00
39d68f17a2
chore(deps): update dependency @types/node to v18.16.14
2023-05-22 08:11:22 +00:00
528dcfe324
fix(support): update dependency @types/semver to v7.5.0
2023-05-21 13:12:03 +00:00
4d7f39b5f8
chore(deps): update dependency eslint to v8.41.0
2023-05-21 10:36:29 +00:00
8594d13bf6
fix(execute-driver-plugin): update dependency vm2 to v3.9.19
2023-05-21 08:10:32 +00:00
a0b434dff7
fix(doctor): update dependency appium-adb to v9.11.3
2023-05-20 13:03:53 +00:00
19a5ae4537
chore(docutils): update dependency mkdocs-material to v9.1.14
2023-05-20 11:23:01 +00:00
fc831d2475
chore(deps): update eslint-related packages to v5.59.6
2023-05-20 11:19:08 +00:00
cb1a97fc8e
chore(deps): update dependency midnight-smoker to v2.0.4
2023-05-20 08:02:34 +00:00
a506a0a357
chore: publish
...
- appium@2.0.0-beta.71
- @appium/base-driver@9.3.10
- @appium/base-plugin@2.2.10
- @appium/fake-plugin@3.1.14
2023-05-19 16:47:14 -07:00
63a429c53b
fix(base-driver): add missing @types/lodash
...
- the lack of this module was causing base-driver to fail to compile when installed as a production module. generally, nobody is going to do such a thing--consumers will use the generated `.d.ts` files--UNLESS they happen to be running typedoc against their extension.
will need to figure out a way to test this to make sure it doesnt happen again.
2023-05-19 16:45:54 -07:00
922725b4f1
chore: publish
...
- appium@2.0.0-beta.70
- @appium/docutils@0.3.13
2023-05-19 15:24:13 -07:00
f0ebe2e02f
fix(docutils): fix broken executable
2023-05-19 15:22:46 -07:00
2ca1581870
chore: publish
...
- appium@2.0.0-beta.69
- @appium/docutils@0.3.12
2023-05-19 14:56:44 -07:00
6aec50b074
chore(docutils): lint
...
- consolidate some eslint overrides
2023-05-19 13:42:08 -07:00
renovate[bot]