I'd like to merge a fix for a MSVC warning in one of the tests: https://github.com/boostorg/nowide/pull/208

I’m requesting to merge a bugfix[1] into Math for Ellint2 that was reported to us through the MSVC STL. This fix is on develop and has cycled green with the linked PR to master. Matt [1] https://github.com/boostorg/math/pull/1379

El 11/03/2026 a las 15:11, Marshall Clow via Boost escribió:

Hi,

The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:

https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy

The next deadline: On April 1st, the master branch closes for all changes.

As always, the calendar is athttps://www.boost.org/calendar

I request permission to merge these two PRs in Boost.Unordered: * https://github.com/boostorg/unordered/pull/345 : a trivial security patch with some Node.js vulnerabilities in the Antora setup for doc building. * https://github.com/boostorg/unordered/pull/334 : this solves an interoperability problem with Boost.LEAF (https://github.com/boostorg/unordered/issues/331). Technically, the fix breaks backwards compatibility, but it does so in scenarios that seem very unlikely (plus the user-side fix is trivial). Joaquín M López Muñoz

Requesting permission to merge to the master branch of LexicalCast the following commit https://github.com/boostorg/lexical_cast/commit/4b0d10a1f3ec33f7aac28dbf03b1... Best regards, Antony Polukhin On Wed, Mar 11, 2026, 17:12 Marshall Clow via Boost <boost@lists.boost.org> wrote:

Hi,

The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:

https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy

The next deadline: On April 1st, the master branch closes for all changes.

As always, the calendar is at https://www.boost.org/calendar

— The release managers _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/PVY2BNKD...

I'd like to merge the commits from this PR to master: https://github.com/boostorg/msm/pull/201 They fix a bug related to errorneous transition selection as well as warnings about redundant semicolons if -Wpedantic is active. They also fix ODR violations in test code in case multiple tests are linked into a single executable.

Hi, I ask for permission to merge two patches from develop to master in Boost.Histogram fix: support sparse storage with accumulators (#421) https://github.com/boostorg/histogram/pull/421 Remove dependencies on Boost.StaticAssert. (#419) https://github.com/boostorg/histogram/pull/419 #419 is trivial. #421 fixes a bug which we apparently had for a long time, but which people now discovered because they found a use-case for histograms with sparse storage, something which we supported since the beginning, but we forgot to test the combination of sparse storage and accumulators. Both changes are narrow and pass the tests on Github. On Wed, Mar 11, 2026 at 3:13 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:

Hi,

The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in:

https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy

The next deadline: On April 1st, the master branch closes for all changes.

As always, the calendar is at https://www.boost.org/calendar

— The release managers _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/PVY2BNKD...