-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency @angular/core to v10 [SECURITY] #315
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-@angular/core-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
September 25, 2022 20:56
05b10a4
to
6e283c2
Compare
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
November 20, 2022 13:59
6e283c2
to
7b9519b
Compare
renovate
bot
changed the title
Update dependency @angular/core to v14 [SECURITY]
Update dependency @angular/core to v15 [SECURITY]
Nov 20, 2022
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
2 times, most recently
from
March 25, 2023 03:14
b313e7c
to
75679ac
Compare
renovate
bot
changed the title
Update dependency @angular/core to v15 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Mar 25, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 3, 2023 10:33
75679ac
to
a036d5f
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v15 [SECURITY]
Apr 3, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 3, 2023 12:54
a036d5f
to
36e7b88
Compare
renovate
bot
changed the title
Update dependency @angular/core to v15 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Apr 3, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 17, 2023 09:36
36e7b88
to
b6240f1
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v15 [SECURITY]
Apr 17, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 17, 2023 14:25
b6240f1
to
b740ae5
Compare
renovate
bot
changed the title
Update dependency @angular/core to v15 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Apr 17, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 28, 2023 11:01
b740ae5
to
0b5cacd
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v16 [SECURITY]
May 28, 2023
renovate
bot
changed the title
Update dependency @angular/core to v16 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
May 28, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
2 times, most recently
from
June 4, 2023 08:00
649fb94
to
550666a
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v16 [SECURITY]
Jun 4, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
June 4, 2023 11:57
550666a
to
a6d221c
Compare
renovate
bot
changed the title
Update dependency @angular/core to v16 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Jun 4, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
June 13, 2023 15:07
a6d221c
to
428c5c0
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v16 [SECURITY]
Jun 13, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
June 13, 2023 18:39
428c5c0
to
e23aab0
Compare
renovate
bot
changed the title
Update dependency @angular/core to v16 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Jun 13, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
June 18, 2023 09:21
e23aab0
to
4182a09
Compare
renovate
bot
changed the title
Update dependency @angular/core to v11 [SECURITY]
Update dependency @angular/core to v16 [SECURITY]
Jun 18, 2023
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
June 18, 2023 13:53
4182a09
to
4c211e6
Compare
renovate
bot
changed the title
Update dependency @angular/core to v16 [SECURITY]
Update dependency @angular/core to v11 [SECURITY]
Jun 18, 2023
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
Mar 24, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 14, 2024 11:11
0db92bb
to
93743fa
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
Apr 14, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 14, 2024 13:49
93743fa
to
f7709db
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
Apr 14, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 21, 2024 07:37
f7709db
to
0667e66
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 21, 2024 09:41
0667e66
to
5858597
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 25, 2024 10:40
5858597
to
8114509
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
Apr 25, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 25, 2024 14:44
8114509
to
30d03d2
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
Apr 25, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 28, 2024 00:29
30d03d2
to
edbaff3
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
Apr 28, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
April 28, 2024 04:09
edbaff3
to
0072bbb
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
Apr 28, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 1, 2024 09:34
0072bbb
to
71dd410
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
May 1, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 1, 2024 13:12
71dd410
to
4006192
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
May 1, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 9, 2024 11:48
4006192
to
2e63a99
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
May 9, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 9, 2024 17:15
2e63a99
to
809deb4
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
May 9, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 15, 2024 10:15
809deb4
to
0e84f7b
Compare
renovate
bot
changed the title
Update dependency @angular/core to v10 [SECURITY]
Update dependency @angular/core to v17 [SECURITY]
May 15, 2024
renovate
bot
force-pushed
the
renovate/npm-@angular/core-vulnerability
branch
from
May 15, 2024 20:33
0e84f7b
to
2138960
Compare
renovate
bot
changed the title
Update dependency @angular/core to v17 [SECURITY]
Update dependency @angular/core to v10 [SECURITY]
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~7.2.0
->~10.2.5
GitHub Vulnerability Alerts
CVE-2021-4231
A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been classified as problematic. Affected is the handling of comments. The manipulation leads to cross site scripting. It is possible to launch the attack remotely but it might require an authentication first. Upgrading to version 10.2.5, 11.0.5 or 11.1.0-next.3 is advised to to address this issue.
Release Notes
angular/angular (@angular/core)
v10.2.5
Compare Source
v10.2.4
Compare Source
v10.2.3
Compare Source
v10.2.2
Compare Source
v10.2.1
Compare Source
v10.2.0
Compare Source
v10.1.6
Compare Source
v10.1.5
Compare Source
v10.1.4
Compare Source
v10.1.3
Compare Source
v10.1.2
Compare Source
v10.1.1
Compare Source
v10.1.0
Compare Source
v10.0.14
Compare Source
v10.0.13
Compare Source
v10.0.12
Compare Source
v10.0.11
Compare Source
v10.0.10
Compare Source
v10.0.9
Compare Source
v10.0.8
Compare Source
v10.0.7
Compare Source
v10.0.6
Compare Source
v10.0.5
Compare Source
v10.0.4
Compare Source
v10.0.3
Compare Source
v10.0.2
Compare Source
v10.0.1
Compare Source
v10.0.0
Compare Source
v9.1.13
Compare Source
v9.1.12
Compare Source
v9.1.11
Compare Source
v9.1.10
Compare Source
v9.1.9
Compare Source
v9.1.8
Compare Source
v9.1.7
Compare Source
v9.1.6
Compare Source
v9.1.5
Compare Source
v9.1.4
Compare Source
v9.1.3
Compare Source
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.7
Compare Source
v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
v8.2.14
Compare Source
v8.2.13
Compare Source
v8.2.12
Compare Source
v8.2.11
Compare Source
v8.2.10
Compare Source
v8.2.9
Compare Source
v8.2.8
Compare Source
v8.2.7
Compare Source
v8.2.6
Compare Source
v8.2.5
Compare Source
v8.2.4
Compare Source
v8.2.3
Compare Source
v8.2.2
Compare Source
v8.2.1
Compare Source
v8.2.0
Compare Source
v8.1.3
Compare Source
v8.1.2
Compare Source
v8.1.1
Compare Source
v8.1.0
Compare Source
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
Breaking Changes
router
come from the injector heirarchy of the routes and never inherit from
the
RouterOutlet
. This means that providers available only to thecomponent that defines the
RouterOutlet
will no longer be available toroute components in any circumstances. This was already the case
whenever routes defined providers, either through lazy loading an
NgModule
or through explicitproviders
on the route config.compiler
FatalDiagnosticError
, hide themessage
field without affecting the emit (#55160)compiler-cli
core
setTimeout
andrAF
references (#55124)ChainedInjector
s in injector debug utils (#55144)forms
language-service
migrations
platform-browser
router
RedirectCommand
(#54556)RouterOutlet
EnvironmentInjector
(#54265)v7.2.16
Compare Source
v7.2.15
Compare Source
v7.2.14
Compare Source
v7.2.13
Compare Source
v7.2.12
Compare Source
v7.2.11
Compare Source
v7.2.10
Compare Source
v7.2.9
Compare Source
v7.2.8
Compare Source
v7.2.7
Compare Source
v7.2.6
Compare Source
v7.2.5
Compare Source
v7.2.4
Compare Source
v7.2.3
Compare Source
common
AsyncPipe
should not callmarkForCheck
on subscription (#54554)compiler-cli
core
@defer
block (#52881)migrations
v7.2.2
Compare Source
common
compiler
compiler-cli
core
migrations
router
v7.2.1
Compare Source
compiler-cli
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.