Skip to content

Bump to v1.16.0#488

Merged
SanjulaGanepola merged 1 commit intomainfrom
v1.16.0
Jan 30, 2026
Merged

Bump to v1.16.0#488
SanjulaGanepola merged 1 commit intomainfrom
v1.16.0

Conversation

Signed-off-by: Sanjula Ganepola <Sanjula.Ganepola@ibm.com>
@github-actions
Copy link

👋 A new build is available for this PR based on 56faeb0.

@SanjulaGanepola SanjulaGanepola marked this pull request as draft January 16, 2026 00:19
@sebjulliand
Copy link
Member

Added #489 to the batch.
@SanjulaGanepola : we should use GitHub's Milestones next time 😅

@SanjulaGanepola
Copy link
Member Author

Indeed should have used Milestones! Will keep that in mind for the next one

@sebjulliand
Copy link
Member

Added #495

@SanjulaGanepola
Copy link
Member Author

@sebjulliand I assume that one is safe to merge since there is a mapepire-server release already? I ended up dropping the visual explain graph PR from this set as I am potentially planning to do a re-work on that using https://reactflow.dev/ which will take me some more time. I'm going to do a review of the remaining 2 and then hit a release today!

@sebjulliand
Copy link
Member

@sebjulliand I assume that one is safe to merge since there is a mapepire-server release already? I ended up dropping the visual explain graph PR from this set as I am potentially planning to do a re-work on that using https://reactflow.dev/ which will take me some more time. I'm going to do a review of the remaining 2 and then hit a release today!

@SanjulaGanepola , yes, totally. 2.3.4 is already out and ready. And it contains a very minor change.

While testing, I just figured out that the way Code for i will update it will make the Db2 for i extension re-upload its version if it's different from Code for i's.
This will be fixed once Code for i v3 is out and we'll update Db2 to not manage the server component install/update. But in the meantime, if both use the same version, it will all be fine.

@sebjulliand
Copy link
Member

@SanjulaGanepola can't wait see how the VE graphs are going to look...that sounds very promising!

@SanjulaGanepola SanjulaGanepola marked this pull request as ready for review January 30, 2026 20:53
@SanjulaGanepola SanjulaGanepola requested review from a team and forstie January 30, 2026 20:53
Copy link
Member

@worksofliam worksofliam left a comment

Choose a reason for hiding this comment

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

ship it

@SanjulaGanepola SanjulaGanepola merged commit 971e7a8 into main Jan 30, 2026
1 check passed
Copy link
Collaborator

@forstie forstie left a comment

Choose a reason for hiding this comment

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

Agree!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants