generated from esm-bundle/autopublish-template
-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 angular monorepo to v19 (major) #183
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-angular-monorepo
base: main
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
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 3, 2023 18:38
de2ab87
to
ff5a67c
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
May 17, 2023 19:56
a99cfff
to
b3fdb47
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
May 24, 2023 19:15
b3fdb47
to
ad1d762
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 1, 2023 18:28
bfe9edf
to
b45d400
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 14, 2023 20:33
4bcca20
to
a345f4f
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
June 28, 2023 16:05
a57feb5
to
87dd7b2
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 5, 2023 23:13
b379c36
to
37e2b64
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
July 13, 2023 21:21
932d782
to
ccea1d5
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 26, 2023 16:20
b2e3c5b
to
898821a
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 9, 2023 21:01
ab41433
to
e91b93b
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 16, 2023 20:10
069f19c
to
906f49e
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
3 times, most recently
from
August 30, 2023 18:33
ccee06b
to
47f5dc4
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
September 13, 2023 19:27
9cf2a5c
to
b3f5443
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
July 24, 2024 23:15
fba72b6
to
02812b1
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
July 31, 2024 19:49
02812b1
to
2e15ab0
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 14, 2024 16:52
1fc03b7
to
d804b6d
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
August 28, 2024 22:19
ed3d878
to
b2ee2f9
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
September 4, 2024 17:02
b2ee2f9
to
657ad89
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
September 18, 2024 18:44
e75c58b
to
568692e
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
October 2, 2024 13:23
d9c3bb9
to
4d4cf2c
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
October 10, 2024 14:30
4d4cf2c
to
d4feea5
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
October 30, 2024 19:35
06524ed
to
4afd660
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
November 6, 2024 18:17
4afd660
to
e9601e8
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
November 19, 2024 17:16
343da3f
to
f62b3ac
Compare
renovate
bot
changed the title
Update angular monorepo to v18 (major)
Update angular monorepo to v19 (major)
Nov 19, 2024
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
November 26, 2024 19:16
f62b3ac
to
9be51d3
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
December 4, 2024 19:47
b16c943
to
a3c769c
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
December 18, 2024 20:11
b1ae5fe
to
ed88b2a
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
January 8, 2025 22:10
80aa590
to
b08f3d1
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
2 times, most recently
from
January 16, 2025 14:15
9181736
to
0a578d4
Compare
renovate
bot
force-pushed
the
renovate/major-angular-monorepo
branch
from
January 20, 2025 17:15
0a578d4
to
fd4e544
Compare
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:
15.2.10
->19.1.2
15.2.10
->19.1.2
15.2.10
->19.1.2
15.2.10
->19.1.2
Release Notes
angular/angular (@angular/compiler)
v19.1.2
Compare Source
compiler
@ng/component
URL to be relative (#59620)compiler-cli
core
Resource
to use explicitundefined
in its typings (#59024)_ejsa
when app is destroyed (#59492)equal
as part of computation (#55818)v19.1.1
Compare Source
core
platform-browser
v19.1.0
Compare Source
common
compiler
compiler-cli
core
migrations
platform-browser
router
events
on dispose (#59327)v19.0.7
Compare Source
compiler-cli
core
migrations
v19.0.6
Compare Source
compiler-cli
core
effect
never run. (#59415)platform-browser
router
v19.0.5
Compare Source
core
on timer
andon idle
on the server (#59177)platform-server
v19.0.4
Compare Source
compiler-cli
core
platform-browser
v19.0.3
Compare Source
v19.0.2
Compare Source
compiler-cli
core
migrations
platform-server
v19.0.1
Compare Source
compiler-cli
core
forms
language-service
migrations
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.13
Compare Source
migrations
v18.2.12
Compare Source
compiler-cli
v18.2.11
Compare Source
core
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.