41c6f7a079
build: update dev-infra shared code to latest revision ( #46292 )
...
Updates dev-infra to the latest revision. This revision supports
for custom release prechecks and performs the release build
before the staging, verifying integrity later. This has various
benefits for stability and making the less less relucant to build
issues that mess up a previously-merged staging PR.
PR Close #46292
2022-06-07 11:50:17 -07:00
f7c9ac16ea
build: update angular ( #45469 )
...
PR Close #45469
2022-03-29 13:13:08 -07:00
2e79d09d85
build: update angular to 5a82e60 ( #45443 )
...
Update the `@angular/dev-infra-private` package to the latest commit.
PR Close #45443
2022-03-25 13:45:06 -07:00
de9290096c
build: update angular ( #45239 )
...
Updates Angular through Renovate. Patch port.
PR Close #45239
2022-03-03 09:14:08 -08:00
7379d75782
ci: add permissions to current github action workflows ( #45177 )
...
The currently recommended best practice for Github action workflows is to set top-level permissions to read only. And if the job uses the automatic `GITHUB_TOKEN`, fine-grained permissions for each job based on the job's requirements should also be added.
All existing workflows in the repository now have top-level read only permission blocks.
Only the `scorecard` workflow currently requires additional job level permissions and the minimum set of permissions were already present for the job.
PR Close #45177
2022-02-24 21:39:38 +00:00
d8a18717da
build: update angular ( #45040 )
...
Update Angular packages to latest versions.
PR Close #45040
2022-02-10 09:16:14 -08:00
d0b88a6810
build: update angular ( #44981 ) ( #45027 )
...
Updates Angular
PR Close #44981
PR Close #45027
2022-02-09 10:18:09 -08:00
881d4696a2
build: update angular ( #44911 )
...
Updates to the latest version of Angular.
PR Close #44911
2022-01-31 21:28:25 +00:00
b89ee0819b
build: update angular ( #44876 )
...
Updates to the latest versions of Angular organization NPM packages.
PR Close #44876
2022-01-28 17:50:15 +00:00
35345b607c
build: update angular ( #44728 )
...
PR Close #44728
2022-01-18 09:24:43 -08:00
5df46650b5
build: update angular ( #44440 )
...
PR Close #44440
2022-01-13 18:30:52 +00:00
02bc4582ba
build: update angular ( #44490 )
...
Updates Angular and the dev-infra package to the latest
version/build.
PR Close #44490
2022-01-04 12:14:14 -08:00
7b6ca4c5d2
build: update angular ( #44273 )
...
PR Close #44273
2021-12-10 16:39:05 -05:00
a0177c6a3a
build: update angular ( #44241 )
...
PR Close #44241
2021-11-23 17:10:24 +00:00
53bdbc6d2c
build: update angular ( #44221 )
...
PR Close #44221
2021-11-19 19:44:55 +00:00
6d8a889898
build: update angular ( #44145 )
...
PR Close #44145
2021-11-18 10:17:14 -08:00
4809bbd83c
build: update angular ( #44074 )
...
PR Close #44074
2021-11-10 20:41:38 +00:00
595a7e3dcd
build: update angular ( #44024 )
...
PR Close #44024
2021-11-03 15:06:36 -07:00
08234f9499
build: update angular ( #43583 )
...
PR Close #43583
2021-11-02 17:31:58 -07:00
643cdf72ee
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:34 +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
Paul Gschwendtner