Skip to content

docs: release notes for the v19.2.24 release#32968

Merged
dgp1130 merged 1 commit intoangular:mainfrom
dgp1130:changelog-cherry-pick-19.2.24
Apr 8, 2026
Merged

docs: release notes for the v19.2.24 release#32968
dgp1130 merged 1 commit intoangular:mainfrom
dgp1130:changelog-cherry-pick-19.2.24

Conversation

@dgp1130
Copy link
Copy Markdown
Collaborator

@dgp1130 dgp1130 commented Apr 8, 2026

Cherry-picks the changelog from the "19.2.x" branch to the next branch (main).

@dgp1130 dgp1130 added the action: merge The PR is ready for merge by the caretaker label Apr 8, 2026
@angular-robot angular-robot bot added the area: docs Related to the documentation label Apr 8, 2026
@dgp1130 dgp1130 force-pushed the changelog-cherry-pick-19.2.24 branch from 89174a8 to 55d4857 Compare April 8, 2026 21:36
@dgp1130 dgp1130 merged commit c304523 into angular:main Apr 8, 2026
6 of 7 checks passed
@dgp1130 dgp1130 deleted the changelog-cherry-pick-19.2.24 branch April 8, 2026 21:36
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the CHANGELOG.md by adding a new entry for version 19.2.24 and applying minor formatting adjustments to existing sections. A review comment points out that the new version entry and the CHANGELOG SPLIT MARKER are incorrectly positioned at the top of the file, which breaks the descending version order relative to version 22.0.0-next.5 and may disrupt automated release processes.

I am having trouble creating individual review comments. Click here to see my feedback.

CHANGELOG.md (1-11)

medium

The CHANGELOG SPLIT MARKER and the new release entry for 19.2.24 are being placed at the very top of the file, above the existing 22.0.0-next.5 entry. This presents two issues:

  1. Version Order: Changelog entries should follow a descending version order. Since 22.0.0-next.5 is a higher version, it should remain at the top of the main branch changelog.
  2. Split Marker: This marker is typically used by automated release scripts to determine where to truncate or archive the changelog. Placing it here will likely cause the 22.0.0-next.5 entry and all subsequent history to be incorrectly archived or omitted from the primary changelog view.

Please move the 19.2.24 section to its correct chronological/versioned position and ensure the split marker is not incorrectly placed above newer versions.

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