Repository navigation
chore: release 1.1.1 - #272
Merged
siracozmen01 merged 2 commits intoNov 5, 2026
Merged
Conversation
siracozmen01
marked this pull request as ready for review
November 5, 2026 00:54
siracozmen01
deleted the
release-please--branches--main--components--maul-unicode
branch
November 5, 2026 01:56
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
1.1.1 (2026-11-04)
Fixed
MUNI_NODISCARDwas empty under GCC 14 in C23, since GCC 14 reportsits C23 as
__STDC_VERSION__202000L and the macro waited for202311L, so a program built with GCC 14 could drop any status the
library returns without a warning. In C the macro now takes
[[nodiscard]]in any dialect after C17 whose compiler has theattribute. A program that drops a status now gets
-Wunused-resultfrom GCC 14 too, which-Werrormakes an error(#271).
No results change: the Unicode data is still 18.0.0 and
MUNI_RESULTS_VERSIONstays 2, so stored normalized keys, skeletonsand verdicts from 1.1.0 stay valid.
This PR was generated with Release Please. See documentation.