Skip to content

Update mimalloc-version to 2.3.0 from 2.2.3#4

Open
zosopentoolsmain wants to merge 1 commit intomainfrom
bump-mimalloc-version-2.3.0
Open

Update mimalloc-version to 2.3.0 from 2.2.3#4
zosopentoolsmain wants to merge 1 commit intomainfrom
bump-mimalloc-version-2.3.0

Conversation

@zosopentoolsmain
Copy link
Copy Markdown

No description provided.

@augmentcode
Copy link
Copy Markdown

augmentcode Bot commented Apr 16, 2026

🤖 Augment PR Summary

Summary: Bumps the pinned mimalloc stable version from 2.2.3 to 2.3.0.
Why: Keeps the port tracking the latest upstream stable tag (v2.3.0) used for STABLE builds.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Copy Markdown

@augmentcode augmentcode Bot left a comment

Choose a reason for hiding this comment

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

Review completed. 1 suggestion posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

Comment thread buildenv
# Update bump details accordingly. Use bump check to confirm.
# bump: mimalloc-version /MIMALLOC_VERSION="(.*)"/ https://github.com/microsoft/mimalloc.git|re:/(^\s*2\.[0-9.]+)/$1/|semver:*
MIMALLOC_VERSION="2.2.3" # Specify a stable release
MIMALLOC_VERSION="2.3.0" # Specify a stable release
Copy link
Copy Markdown

@augmentcode augmentcode Bot Apr 16, 2026

Choose a reason for hiding this comment

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

Changing MIMALLOC_VERSION also changes ZOPEN_STABLE_TAG to v2.3.0; can you confirm the existing patches/* still apply cleanly against that upstream tag? A version-only bump can otherwise fail later during the patch step/build even though this diff is small.

Severity: medium

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

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.

1 participant