chore: update dependencies #1126
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/dependencies
branch
5 times, most recently
from
842fc6d to
8d4374e
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
50a6505 to
1849c6b
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
4 times, most recently
from
811a764 to
92654c5
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
4 times, most recently
from
f67d717 to
1bd20e2
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
9 times, most recently
from
e020120 to
a79c7e7
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
5 times, most recently
from
faed9c7 to
b16ee0a
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
b16ee0a to
22ad483
Compare
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.
Update Request | Renovate Bot
This PR contains the following updates:
10.44->10.453.7->3.86.11.0->6.12.06.12.11->6.12.12cc38d7d->77cc3edv3.1.7->v4.0.32.5.5->2.6.0v0.4.0-1-g76a2c8f->v0.4.0Release Notes
PCRE2Project/pcre2 (PCRE2Project/pcre2)
v10.45Compare Source
(#418) Change 6 of 10.44 broke 32-bit tests because pcre2test's reporting of
memory size was changed to the entire compiled data block, instead of just the
pattern and tables data, so as to align with the new length restriction.
Because the block's header contains pointers, this meant the pcre2test output
was different in 32-bit mode. A patch by Carlo reverts to the previous state
and makes sure that any limit set by pcre2_set_max_pattern_compiled_length()
also avoids the internal struct overhead.
(#416, #622) Updates to build.zig.
(#427, et al.) Various fixes to pacify static analyzers.
(#428) Add --posix-pattern-file to pcre2grep to allow processing of empty
patterns through the -f option, as well as patterns that end in space
characters, for compatibility with other grep tools.
(
4fa5b8b) Fix a bug in the fuzz support quantifier-limiting code. It ignoresstrings of more than 5 digits because they are necessarily numbers greater than
65535, the largest legal quantifier. However, it wasn't ignoring non-significant
leading zeros.
(
6d82f0c) The case-independent processing of the letter-matching Unicodeproperties Ll, Lt, and Lu have been changed to match Perl (which changed a while
ago). When caseless matching is in force, all three of these properties are now
treated as Lc (cased letter).
(#433) The pcre2_jit_compile() function was updated by the addition of a new
option PCRE2_JIT_TEST_ALLOC which, if called with a NULL first argument, tests
not only the availability of JIT, but also its ability to allocate executable
memory. Update pcre2test to use this support to extend the -C option.
(
75b1025) The code for parsing Unicode property descriptions for \p and \Pbeen changed as follows:
. White space etc. before ^ in a negated value such as \p{ ^L } was not being
ignored.
. The code wouldn't have worked if PCRE2 was compiled for UTF-8 support
within an EBCDIC environment. Possibly nobody does this any more, but it
should now work.
. The documentation of the syntax of what can follow \p and \P has been
updated.
(
1c24ba0) There was an error in the table of lengths for parsed items forthe OPTIONS item, but fortuitously it could never have actually bitten. While
fixing this, some other code that could never be obeyed was discovered and
removed.
(
674b664) Removed some incorect optimization code from DFA matching thathas been there since PCRE1, but has just been found to cause a no match return
instead of a partial match in some cases. It involves partial matching when (*F)
is present so is unlikely to have actually affected anyone.
(
b0f4ac1) Tidy the wording and formatting of some pcre2test error messagesconcerned with bad modifiers. Also restrict single-letter modifier sequences to
the first item in a modifier list, as documented and always intended.
(
1415565) An iterator at the end of many assertions can always beauto-possessified, but not at the end of variable-length lookbehinds. There was
a bug in the code that checks for such a lookbehind; it was looking only at the
first branch, which is wrong because some branches can be fixed length when
others are not, for example (?<=AB|CD?). Now all branches are checked for
variability.
(
ead0828) Matching with pcre2_match() could give an incorrect result if avariable-length lookbehind was used as the condition in a conditional group.
The condition could erroneously be treated as true if a branch matched but
overran the current position. This bug was in the interpreter only; matching
with JIT was correct.
(#443) Split out the sljit sub-project into a "Git submodule". Git users
must now run
git submodule init; git submodule updateafter a Git checkout, orthe build will fail due to missing files in deps/sljit.
(#441) Add a new error code (PCRE2_ERROR_JIT_UNSUPPORTED) which is yielded
for unsupported jit features.
(#444) Fix bug in 'first code unit' and 'last code unit' optimization
combined with lookahead assertions.
(#445, #447, #449, #451, #452, #459, #563) Add a new feature called scan
substring. This feature is a new type of assertion which matches the content of
a capturing block to a sub-pattern.
(#450) Improvements to 'first code unit' / 'starting code units'
optimisation.
(#455) Many, many improvements to the JIT compiler.
Item 43 of 10.43 was incomplete because it addressed only \z and not \Z,
which was still misbehaving when matching fragments inside invalid UTF strings.
(
d29e729) Octal escapes of the form \045 or \111 were not being recognizedin substitution strings, and if encountered gave an error, though the \o{...}
form was recognized. This bug is now fixed.
(#463, #487) Fix 1 byte out-of-bounds read when parsing malformed limits
(e.g. LIMIT_HEAP)
Many improvements to test infrastructure. Many more platforms and
configurations are now run in Continuous Integration, and all the platforms now
run the full test suite, rather than a partial subset.
(#475) Implement title casing in substitution strings using Perl syntax.
(#478, #504) Disallow \x if not followed by { or a hex digit.
(#473) Implements Python-style backrefs in substitutions.
(#472) Fix error reporting for certain over-large octal escapes.
(#482) Fix parsing of named captures in replacement strings, allowing
non-ASCII capture names to be used.
(#477, #474, #488, #494, #496, #506, #508, #511, #518, #524, #540) Many
improvements to parsing and optimising of character classes.
(#483, #498) Add support for \g and $ to replacement strings.
(#470) Add option flags PCRE2_EXTRA_NO_BS0 and PCRE2_EXTRA_PYTHON_OCTAL.
(#471) Add new API function pcre2_set_optimize() for controlling which
optimizations are enabled.
(#491) Adds$& $ ` $' and $_ to substitution replacements, as well as
interpreting \b and \v as characters.
(#499) Add option PCRE2_EXTRA_NEVER_CALLOUT to disable callouts.
(#503, #513) Update Unicode support to UCD 16.
(#512, #618, #638) Add new function pcre2_set_substitute_case_callout() to
allow clients to provide a custom callback with locale-aware case
transformation.
(#516) Fix case-insensitive matching of backreferences when using the
PCRE2_EXTRA_CASELESS_RESTRICT option.
(#519) In pcre2grep, add $& as an alias for $0
(
c9bf833, #534) Updated perltest.sh to enable locale setting.(#521) Add support for Turkish I casefolding, using new options
PCRE2_EXTRA_TURKISH_CASING, and added pre-pattern flags (*TURKISH_CASING) and
(*CASELESS_RESTRICT).
(#523, #546, #547) Add support for UTS#18 compatible character classes,
using the new option PCRE2_ALT_EXTENDED_CLASS. This adds '[' as a metacharacter
within character classes and the operators '&&', '--' and '~~', allowing
subtractions and intersections of character classes to be easily expressed.
(#553, #586, #596, #597) Add support for Perl-style extended character
classes, using the syntax (?[...]). This also allows expressing subtractions and
intersections of character classes, but using a different syntax to UTS#18.
(#554) Fixed a bug in JIT affecting greedy bounded repeats. The upper limit
of repeats inside a repeated bracket might be incorrectly checked.
(#556) Fixed a bug in JIT affecting caseful matching of backreferences. When
utf is disabled, and dupnames is enabled, caseless matching was used even
if caseful matching was needed.
(
f34fc0a) Fixed a bug in pcre2grep reported by Alejandro Colomar[email protected] (GitHub issue #577). In certain cases, when lines of above and
below context were contiguous, a separator line was incorrectly being inserted.
(#594) Fix a small (one/two byte) out-of-bounds read on invalid UTF-8 input
in pcre2grep.
(#370) Fix the INSTALL_MSVC_PDB CMake flag.
(#366) Install cmake files in prefix/lib/cmake/pcre2 rather than
prefix/cmake. The new CMake flag PCRE2_INSTALL_CMAKEDIR allows customising this
location.
(#624, #626, #628, #632, #639, #641) Reduce code size of generated JIT code
for repeated character classes.
(#623) Update the Bazel build files.
SELinuxProject/selinux (SELinuxProject/selinux)
v3.8: SELinux userspace release 3.8Compare Source
RELEASE 3.8
Important change:
The internal representation of file_contexts.*.bin files is completely
rewritten and new format stores all multi-byte data in network
byte-order, so that such compiled files can be cross-compiled,
e.g. for embedded devices with read-only filesystems.
User-visible changes
libsemanage: Preserve file context and ownership in policy store
libselinux: deprecate security_disable(3)
libsepol: Support nlmsg extended permissions
libsepol: Add policy capability netlink_xperm
libsemanage: Optionally allow duplicate declarations
policycoreutils: introduce unsetfiles
libselinux/utils: introduce selabel_compare
improved selabel_lookup performance
libselinux: support parallel usage of selabel_lookup(3)
libsepol: add support for xperms in conditional policies
Improved man pages
Code improvements and bug fixes
Always build for LFS mode on 32-bit archs.
libsemanage: Mute error messages from selinux_restorecon introduced in 3.8-rc1
Regex spec ordering is restored to pre 3.8-rc1
Binary fcontext files format changed, files using old format are ignored
Code improvements and bug fixes
apparmor/apparmor (https://gitlab.com/apparmor/apparmor.git)
v4.0.3: AppArmor 4.0.3Compare Source
AppArmor 4.0.3 is a bug fix release of the user space components of the AppArmor security project. The kernel portion of the project is maintained and pushed separately.
This version of the userspace should work with all kernel versions from 2.6.15 and later (some earlier version of the kernel if they have the apparmor patches applied).
Obtaining the Release
There are two ways to obtain this release either through gitlab or a tarball in launchpad.
Important note: the gitlab release tarballs differ from the launchpad release tarballs. The launchpad release tarball has a couple processing steps already performed:
autogen.shis already done, meaning distros only need to use ./configure in their build setupgitlab
v4.0.2: AppArmor 4.0.2Compare Source
AppArmor 4.0.2 is a bug fix release of the user space components of the AppArmor security project. The kernel portion of the project is maintained and pushed separately.
This version of the userspace should work with all kernel versions from
2.6.15 and later (some earlier version of the kernel if they have the
apparmor patches applied).
Important Note
AppArmor 4.0.2 does not address interactions between the bwrap_userns_restrict and flatpak profiles. The bwrap profile is not enabled by default, if enabled the flatpak profile needs to be updated.
Obtaining the Release
There are two ways to obtain this release either through gitlab or a tarball in launchpad.
Important note: the gitlab release tarballs differ from the launchpad release tarballs. The launchpad release tarball has a couple processing steps already performed:
autogen.shis already done, meaning distros only need to use ./configure in their build setupgitlab
v4.0.1: AppArmor 4.0Compare Source
AppArmor 4.0 is a major new release of the AppArmor that is in development.
Apprmor 4.0 is a bridge release between older AppArmor 3.x policy and the newer AppArmor 4 style policy which introduces several new features that are not backwards compatible. As such AppArmor 4.0 will be a short lived release, and will not receive long term support. The following AppArmor 4.1 feature release is planned to be a regular release, please take this into account when including AppArmor 4.0 into a distro release. For questions around compatibility see the compatibility matrix.
Note
Obtaining the Release
There are two ways to obtain this release either through gitlab or a tarball in launchpad.
Important note: the gitlab release tarballs differ from the launchpad release tarballs. The launchpad release tarball has a couple processing steps already performed:
autogen.shis already done, meaning distros only need to use ./configure in their build setupgitlab
v4.0.0Compare Source
seccomp/libseccomp (seccomp/libseccomp)
v2.6.0: libseccomp v2.6.0Compare Source
ChangeLog
seccomp_transaction_start(),seccomp_transaction_commit(), andseccomp_transaction_reject()APIsseccomp_precompute()API to generate the seccomp BPF filter prior toseccomp_load()orseccomp_export_bpf_mem()Checksum
v2.5.6: libseccomp v2.5.6Compare Source
ChangeLog
Checksum
siderolabs/bldr (siderolabs/bldr)
v0.4.0Compare Source
bldr 0.4.0 (2025-01-31)
Welcome to the v0.4.0 release of bldr!
Please try out the release binaries and report any issues at
https://github.com/siderolabs/bldr/issues.
Contributors
Changes
7 commits
62ed470release(v0.4.0): prepare release4a79aebfeat: make variant inpkg.yamlexplicitd978bccfix: drop TOOLCHAIN from std vars66b078dfix: drop alpine formd5sumstep24a37b0feat: implement support for network mode40ad501chore: rekres to simplify.kres.yamldefaults73fad60chore: bump depsChanges from siderolabs/gen
4 commits
5ae3afechore: update hashtriemap implementation from the latest upstreame847d2achore: add more utilities to xiterf3c5a2bchore: addEmptyandEmpty2iteratorsc53b90bchore: add packages xiter/xstrings/xbytesDependency Changes
Previous release can be found at v0.3.2
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.