-
Notifications
You must be signed in to change notification settings - Fork 5
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
Story #12962: upgrade angular to 17 #1905
Merged
Merged
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
ebernard
force-pushed
the
angular_17_upgrade
branch
from
June 18, 2024 15:35
afa644b
to
efcb068
Compare
ebernard
changed the title
Story #12961: upgrade angular to 16
Story #12961: upgrade angular to 17
Jun 18, 2024
ebernard
force-pushed
the
angular_17_upgrade
branch
from
June 18, 2024 15:36
efcb068
to
e3cae26
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
2 times, most recently
from
June 18, 2024 15:47
8b3cc36
to
32f1204
Compare
ebernard
force-pushed
the
angular_16_upgrade
branch
5 times, most recently
from
June 18, 2024 18:24
2c55135
to
5dd7793
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
2 times, most recently
from
June 18, 2024 18:40
abb0abe
to
7b60d04
Compare
ebernard
force-pushed
the
angular_16_upgrade
branch
from
June 18, 2024 19:08
5dd7793
to
a5bbd3a
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
from
June 18, 2024 19:14
b37e296
to
c50f6ea
Compare
ebernard
force-pushed
the
angular_16_upgrade
branch
2 times, most recently
from
June 19, 2024 12:24
38f80c8
to
d323679
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
2 times, most recently
from
June 19, 2024 12:43
ed83048
to
03a67d4
Compare
ebernard
changed the title
Story #12961: upgrade angular to 17
Story #12962: upgrade angular to 17
Jun 19, 2024
marob
approved these changes
Jun 19, 2024
ebernard
force-pushed
the
angular_16_upgrade
branch
from
June 20, 2024 07:55
d323679
to
132b506
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
3 times, most recently
from
June 20, 2024 11:13
02db11a
to
df69079
Compare
Regzox
approved these changes
Jun 20, 2024
ebernard
force-pushed
the
angular_16_upgrade
branch
from
June 20, 2024 13:48
132b506
to
494c069
Compare
ebernard
force-pushed
the
angular_17_upgrade
branch
from
June 20, 2024 14:04
df69079
to
06120e8
Compare
No New Or Fixed Issues Found |
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.
Description
Upgrade angular to 17