(release): 25.0.0 - #2290
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
surya-pabbineedi
marked this pull request as ready for review
July 29, 2026 04:44
hemanth-r
approved these changes
Jul 29, 2026
This file contains hidden or 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
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.
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
Package version was still
24.0.0/ changelog underHEAD (unreleased)after the Angular 22 upgrade and Siemens sync landed on master. Publishable lib package atprojects/swimlane/ngx-datatableis already25.0.0.What is the new behavior?
@swimlane/ngx-datatableversion inprojects/ngx-datatable/package.jsonto25.0.0HEAD (unreleased)to## 25.0.0(Angular 22 support, CSS-grid scroll rewrite, Siemens sync features/fixes, and breaking API removals)Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
This release documents breaking changes already merged on master:
sortoutput → use(sortsChange)or[(sorts)]selectoutput → use(selectedChange)or[(selected)]ResizeObserver/ layoutOther information:
Publish after merge using the repo release flow (
yarn package, tag25.0.0,yarn publish).Made with Cursor