-
Notifications
You must be signed in to change notification settings - Fork 6
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 dependencies (major) #927
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-dependencies
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
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.
Open
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
ghost
added
the
in progress
label
Dec 9, 2018
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
2 times, most recently
from
December 14, 2018 07:27
43c7d16
to
c633d9c
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
from
December 18, 2018 23:41
c633d9c
to
57402cd
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
5 times, most recently
from
January 12, 2019 15:23
ef0a52f
to
22100a9
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
January 22, 2019 23:47
dee7f3a
to
53529e6
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
4 times, most recently
from
February 6, 2019 03:56
6123f21
to
e59811d
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
February 20, 2019 20:33
136197e
to
0146a4c
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
2 times, most recently
from
March 3, 2019 17:49
0d90150
to
65ccc5b
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
2 times, most recently
from
March 13, 2019 00:06
a02a5e0
to
d0d41af
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
4 times, most recently
from
March 20, 2019 03:13
2864f21
to
33bbfe7
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
2 times, most recently
from
March 26, 2019 22:38
4bdd172
to
13f53b2
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
6 times, most recently
from
September 22, 2024 07:36
f7b058b
to
df95fb4
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
5 times, most recently
from
September 28, 2024 05:16
996a1a3
to
17e7209
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
October 4, 2024 02:48
5616b19
to
12de2ad
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
October 11, 2024 19:39
13748a5
to
3d82ff4
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
October 27, 2024 16:19
83d6d51
to
cf728a2
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
November 6, 2024 18:02
8334e91
to
fe56eab
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
from
November 7, 2024 06:00
fe56eab
to
4de0ba8
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
3 times, most recently
from
November 19, 2024 18:19
f48cb13
to
c58bdbe
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
from
November 22, 2024 11:50
c58bdbe
to
93b38d9
Compare
renovate
bot
force-pushed
the
renovate/major-dependencies
branch
from
November 22, 2024 15:53
93b38d9
to
9a19234
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
5.2.11
->19.0.0
5.2.11
->19.0.0
5.2.11
->19.0.0
5.2.11
->19.0.0
5.2.11
->7.2.16
5.2.11
->19.0.0
5.2.11
->19.0.0
5.2.11
->19.0.0
5.2.11
->19.0.0
16.8.17
->18.3.12
16.8.4
->18.3.1
4.4.5
->5.1.20
4.3.3
->5.3.3
2.6.5
->3.39.0
^2.2.0
->^3.0.0
16.8.6
->18.3.1
16.8.6
->18.3.1
4.3.1
->7.0.1
5.5.12
->7.8.1
0.21.6
->6.15.1
^3.2.1
->^11.0.0
2.6.10
->3.5.13
3.0.6
->4.4.5
Release Notes
angular/angular (@angular/common)
v19.0.0
Compare Source
Breaking Changes
compiler
this.foo
property reads no longer refer to template context variables. If you intended to read the template variable, do not usethis.
.core
Generally this PR has two implications:
effects which are triggered outside of change detection run as part of
the change detection process instead of as a microtask. Depending on the
specifics of application/test setup, this can result in them executing
earlier or later (or requiring additional test steps to trigger; see below
examples).
effects which are triggered during change detection (e.g. by input
signals) run earlier, before the component's template.
We've seen a few common failure cases:
Tests which used to rely on the
Promise
timing of effects now need toawait whenStable()
or call.detectChanges()
in order for effects torun.
Tests which use faked clocks may need to fast-forward/flush the clock to
cause effects to run.
effect()
s triggered during CD could rely on the application being fullyrendered (for example, they could easily read computed styles, etc). With
the change, they run before the component's updates and can get incorrect
answers. The recent
afterRenderEffect()
API is a natural replacement forthis style of effect.
effect()
s which synchronize with the forms system are particularlytiming-sensitive and might need to adjust their initialization timing.
ExperimentalPendingTasks
has been renamed toPendingTasks
.Angular directives, components and pipes are now standalone by default. Specify for declarations that are currently declared in s. for v19 will take care of this automatically.
The
autoDetect
feature ofComponentFixture
will nowattach the fixture to the
ApplicationRef
. As a result, errors duringautomatic change detection of the fixture be reported to the
ErrorHandler
.This change may cause custom error handlers to observe new failures that were previously unreported.
Render default fallback with empty
projectableNodes
.When passing an empty array to
projectableNodes
in thecreateComponent
API, the default fallback content of theng-content
will be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')
as aprojectableNode
.For example:
Errors that are thrown during
ApplicationRef.tick
will now be rethrown when using
TestBed
. These errors should beresolved by ensuring the test environment is set up correctly to
complete change detection successfully. There are two alternatives to
catch the errors:
it synchronously and expect the error. For example, a jasmine test
could write
expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
TestBed
will reject any outstandingComponentFixture.whenStable
promises. A jasmine test,for example, could write
expectAsync(fixture.whenStable()).toBeRejected()
.As a last resort, you can configure errors to not be rethrown by
setting
rethrowApplicationErrors
tofalse
inTestBed.configureTestingModule
.The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use
fakeAsync
: these timers will now be visible tofakeAsync
and can be affected by
tick
orflush
.The deprecated
factories
property inKeyValueDiffers
has been removed.elements
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
localize
name
option in theng add
@localize`` schematic has been removed in favor of theproject
option.platform-browser
BrowserModule.withServerTransition
method has been removed. Please use theAPP_ID
DI token to set the application id instead.router
Router.errorHandler
property has been removed.Adding an error handler should be configured in either
withNavigationErrorHandler
withprovideRouter
or theerrorHandler
property in the extra options of
RouterModule.forRoot
. In addition,the error handler cannot be used to change the return value of the
router navigation promise or prevent it from rejecting. Instead, if you
want to prevent the promise from rejecting, use
resolveNavigationPromiseOnError
.Resolve
interface now includesRedirectCommand
.common
compiler
typeof
keyword in template expressions. (#58183)this.a
should always refer to class propertya
(#55183):host
parsing in pseudo-selectors (#58681):host:host-context(.foo)
(#58681)compiler-cli
core
standalone: false
. (#57643)run
method onExperimentalPendingTasks
(#56546)undefined
without needing to include it in the type argument ofinput
(#57621)allowSignalWrites
(#57874)resource()
API for async dependencies (#58255)rxResource()
(#58255)standalone
totrue
(#58169)afterRenderEffect
(#57549)outputFromObservable
&outputToObservable
to stable. (#58214)takeUntilDestroyed
to stable. (#58200)@let
syntax (#57813)ViewContext
is retained after closure minification (#57903)None
for empty component styles (#57130)factories
Property inKeyValueDiffers
(#58064)elements
output()
-shaped outputs (#57535)ComponentRef.setInput
& remove custom scheduler (#56728)forms
http
withRequestsMadeViaParent
to stable. (#58221)language-service
@Input
to signal-input (#57214)localize
name
option. (#58063)migrations
ng generate
schematic (#57805)platform-browser
BrowserModule.withServerTransition
method (#58062)platform-server
PlatformRef
when error happens during thebootstrap()
phase (#58112)router
routerOutletData
input toRouterOutlet
directive (#57051)injector
onOutletContext
(#58343)service-worker
v18.2.12
Compare Source
compiler-cli
v18.2.11
Compare Source
core
v18.2.10
Compare Source
compiler
localize
v18.2.9
Compare Source
compiler-cli
v18.2.8
Compare Source
compiler
compiler-cli
core
platform-server
PlatformRef
when error happens during thebootstrap()
phase (#58112) (#58135)v18.2.7
Compare Source
common
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" in timezone Japan, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.