0c1a1421e1
build: update angular ( #44241 )
...
PR Close #44241
2021-11-23 17:10:24 +00:00
6e351ed753
build: update angular ( #44221 )
...
PR Close #44221
2021-11-19 19:44:55 +00:00
76f390be95
build: update angular ( #44145 )
...
PR Close #44145
2021-11-18 10:17:16 -08:00
9c47b77b05
build: sync all lock file and package.json updates from next with patch ( #44134 )
...
With the goal of avoiding more conflicts with build changes that should
go into both patch + next in general, this commit brings the lock files
+ `package.json` files from patch branch to the equivalent contents of
the next branch, except for the actual `version` field.
PR Close #44134
2021-11-10 23:33:11 +00:00
12769e3583
build: update angular ( #44030 )
...
Update all `@angular/*` and `@schematics/*` root dependencies to latest
versions.
PR Close #44030
2021-11-08 16:59:47 +00:00
5d031848d3
ci: update angular/dev-infra/github-actions sha ( #43904 )
...
Consume latest version of `angular/dev-infra/github-actions`.
PR Close #43904
2021-10-21 16:26:36 +00:00
41b8f98744
build: update the lock closed sha to the latest sha ( #41140 )
...
Update to use the latest lock closed sha, additionally use the full length sha for
referencing the exact version to use.
PR Close #41140
2021-03-09 13:24:50 -08:00
246c757c7f
build: update lock-closed GitHub action to latest version ( #39371 )
...
This commit updates the version of the `dev-infra/lock-closed` GitHub
action to the latest version, that includes the fix from
angular/dev-infra#80.
PR Close #39371
2020-10-22 13:46:24 -07:00
90cec40cce
build: bump to lastest sha of angular/dev-infra's lock-closed action ( #38615 )
...
Update to the latest lock-closed action to fix the link which is used.
PR Close #38615
2020-08-27 10:58:29 -07:00
b99b80c18b
fix(dev-infra): do not run the lock-closed GitHub action on forks ( #36000 )
...
Previously, the `lock-closed` GitHub action, which runs daily and locks
closed inactive issues, was run on each fork of the `angular/angular`
repo. While the action is a [no-op on forks][1], it make still fail from
time to time, generating a confusing notification e-mail for the fork
owner.
This commit configures the `lock-closed` action to only run on the main
`angular/angular` repository (using the method suggested [here][2]).
[1]: https://github.com/angular/dev-infra/blob/13b25d383/github-actions/lock-closed/src/main.ts#L117
[2]: https://github.community/t5/GitHub-Actions/Do-not-run-cron-workflows-in-forks/td-p/46756
PR Close #36000
2020-03-11 14:45:47 -04:00
67d08b15e0
ci: fix name of lock-closed workflow ( #32698 )
...
PR Close #32698
2019-09-16 14:14:39 -07:00
d2bf8fac5b
ci: update schedule for locking inactive issues ( #32698 )
...
PR Close #32698
2019-09-16 14:14:39 -07:00
0a0489d3d0
ci: run lock closed issues more frequently during backlog clearing, update to latest version from dev-infra ( #32637 )
...
PR Close #32637
2019-09-12 12:33:47 -04:00
fed6b25be0
ci: move to latest lock-closed commit for github action ( #32502 )
...
PR Close #32502
2019-09-05 18:08:10 -04:00
7bbc3523ba
ci: set up angular-automatic-lock-bot for the repo ( #32500 )
...
PR Close #32500
2019-09-05 14:27:16 -04:00
Renovate Bot