mirror of
https://github.com/appium/appium.git
synced 2026-10-25 18:21:19 +08:00
Christopher Hiller
4def2e926a
1. Uses `sync-monorepo-packages` to keep `README.md` and `packages/appium/README.md` in sync. Since `README` gets published to npm but _also_ shows in the GitHub repo, both places need a `README`. In lieu of a custom `README`, we can just sync it for now. This is called via a `preversion` script. 1. Various fields are synced in `package.json`. This does not include dependencies—but those _in common_ should probably be kept in sync as well. 1. Lerna uses conventional commits and Git tags to figure out what to do. It should automatically determine what needs releasing and what version it should be released as. 1. Tags have been pushed to the repo for Lerna to use. In the case where the changesets are functionally identical to the latest code in the old repositories, the version number has been retained, and the tag is of the format `[@scope/]<package-name>@<version>`. In the case where the old repos had _unreleased_ changesets, I’ve tagged with a new patch release and adopted the `-rc.0` suffix. So if we were at v5.5.0 in `appium-gulp-plugins`, `@appium/gulp-plugins` is tagged as `@appium/gulp-plugins@5.5.1-rc.0`. I have not modified the version in `package.json`. 1. As with adopting any new release/publishing strategy, we should be meticulous about what we’re doing until we’re comfortable with how it works. Lerna supports dry runs; we should use them. 1. Documentation on usage will arrive in next changes to this PR.
24 lines
358 B
JSON
24 lines
358 B
JSON
{
|
|
"ci": false,
|
|
"command": {
|
|
"exec": {
|
|
"ignore": "@appium/eslint-config-appium"
|
|
},
|
|
"version": {
|
|
"push": false,
|
|
"conventionalCommits": true
|
|
}
|
|
},
|
|
"ignoreChanges": [
|
|
"**/test/**",
|
|
"**/*.md"
|
|
],
|
|
"npmClientArgs": [
|
|
"--no-package-lock"
|
|
],
|
|
"packages": [
|
|
"packages/*"
|
|
],
|
|
"version": "independent"
|
|
}
|