Skip to content

Update next branch to reflect new release-train "v20.1.0-next.0". #30219

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

Merged
merged 2 commits into from
Apr 30, 2025

Conversation

jkrems
Copy link
Contributor

@jkrems jkrems commented Apr 30, 2025

The previous "next" release-train has moved into the feature-freeze phase. This PR updates the next branch to the subsequent release-train.

Also this PR cherry-picks the changelog for v20.0.0-next.9 into the main branch so that the changelog is up to date.

@jkrems jkrems added the action: merge The PR is ready for merge by the caretaker label Apr 30, 2025
@angular-robot angular-robot bot added the area: docs Related to the documentation label Apr 30, 2025
@jkrems jkrems merged commit c79a246 into angular:main Apr 30, 2025
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant