cdb5d07606
The components repo and framework repository follow the same patch branch concept. We should be able to share a script for determining these merge branches. Additonally the logic has been improved compared to the old merge script because we no longer consult `git ls-remote` unless really needed. Currently, `git ls-remote` is always consulted, even though not necessarily needed. This can slow down the merge script and the caretaker process when a couple of PRs are merged (personally saw around ~4 seconds per merge). Additionally, the new logic is more strict and will ensure (in most cases) that no wrong patch/minor branch is determined. Previously, the script just used the lexicographically greatest patch branch. This _could_ be wrong when a new patch branch has been created too early, or by accident. PR Close #37217
38 lines
985 B
JSON
38 lines
985 B
JSON
{
|
|
"name": "@angular/dev-infra-private",
|
|
"version": "0.0.0",
|
|
"description": "INTERNAL USE ONLY - Angular internal DevInfra tooling/scripts - INTERNAL USE ONLY",
|
|
"license": "MIT",
|
|
"private": true,
|
|
"bin": {
|
|
"ng-dev": "./cli.js",
|
|
"ts-circular-deps": "./ts-circular-dependencies/index.js"
|
|
},
|
|
"dependencies": {
|
|
"@octokit/graphql": "<from-root>",
|
|
"chalk": "<from-root>",
|
|
"cli-progress": "<from-root>",
|
|
"glob": "<from-root>",
|
|
"inquirer": "<from-root>",
|
|
"minimatch": "<from-root>",
|
|
"multimatch": "<from-root>",
|
|
"semver": "<from-root>",
|
|
"shelljs": "<from-root>",
|
|
"typed-graphqlify": "<from-root>",
|
|
"yaml": "<from-root>",
|
|
"yargs": "<from-root>"
|
|
},
|
|
"peerDependencies": {
|
|
"@bazel/buildifier": "<from-root>",
|
|
"clang-format": "<from-root>",
|
|
"ts-node": "<from-root>",
|
|
"tslib": "<from-root>",
|
|
"typescript": "<from-root>"
|
|
},
|
|
"peerDependenciesMeta": {
|
|
"ts-node": {
|
|
"optional": true
|
|
}
|
|
}
|
|
}
|