illuna-minetest.tk merge requestshttps://git.tchncs.de/Illuna-Minetest/illuna-minetest.tk/-/merge_requests2022-10-05T15:04:18+02:00https://git.tchncs.de/Illuna-Minetest/illuna-minetest.tk/-/merge_requests/41Bump sqlite3 from 1.4.4 to 1.5.22022-10-05T15:04:18+02:00DependabotBump sqlite3 from 1.4.4 to 1.5.2Bumps [sqlite3](https://github.com/sparklemotion/sqlite3-ruby) from 1.4.4 to 1.5.2.
<details>
<summary>Release notes</summary>
*Sourced from [sqlite3's releases](https://github.com/sparklemotion/sqlite3-ruby/releases).*
> ## 1.5.2 / 20...Bumps [sqlite3](https://github.com/sparklemotion/sqlite3-ruby) from 1.4.4 to 1.5.2.
<details>
<summary>Release notes</summary>
*Sourced from [sqlite3's releases](https://github.com/sparklemotion/sqlite3-ruby/releases).*
> ## 1.5.2 / 2022-10-01
>
> ### Packaging
>
> This version correctly vendors the tarball for sqlite v3.39.4 in the vanilla "ruby" platform gem package, so that users will not require network access at installation.
>
> v1.5.0 and v1.5.1 mistakenly packaged the tarball for sqlite v3.38.5 in the vanilla "ruby" platform gem, resulting in downloading the intended tarball over the network at installation time (or, if the network was not available, failure to install). Note that the precompiled native gems were not affected by this issue. [#352](https://github.com/sparklemotion/sqlite3-ruby/issues/352)
>
> ---
>
> sha256 checksums:
>
> ```
> 94626203958f9abf5e7d28b0337af6d00fb10cabfc3d65e70eb95b878080a812 sqlite3-1.5.2-aarch64-linux.gem
> ada7a8ec6b13165ebb56dfc8df9f896d2b41c78e92e2ba0b5bca969b6c376e1d sqlite3-1.5.2-arm-linux.gem
> 472d837f79273bbfb7d626c787a0f3e9f0bd0a3855ed5bfee1ef70bee8808ced sqlite3-1.5.2-arm64-darwin.gem
> 750bf833b72550244c672cb3467b68b5c89b3e8be2c893a2749cdbc3841ee898 sqlite3-1.5.2-x64-mingw-ucrt.gem
> e750e17784cd76b59f5dd9a3366f9b0d76626872700f0f59194f2f4c439cbb01 sqlite3-1.5.2-x64-mingw32.gem
> caf0a7717375addb46157b1090ad02316a9491531d69e2389f56058ce784518e sqlite3-1.5.2-x86-linux.gem
> caff6c75b13874ce828514a95aa437744e042390fdeb0f73decde16235d3fe2f sqlite3-1.5.2-x86_64-darwin.gem
> 245f2ef5dd9c6a2b3df41b4af41fa659c8917d0cc231d4c1b03b4d199ae412e7 sqlite3-1.5.2-x86_64-linux.gem
> 9b3153b5703b4619534135c16ff7c4e8ba1adbd8548ff61bb4a002dd632bcd5e sqlite3-1.5.2.gem
> ```
>
> ## 1.5.1 / 2022-09-29
>
> ### Dependencies
>
> * Vendored sqlite is updated to [v3.39.4](https://sqlite.org/releaselog/3_39_4.html).
>
> ### Security
>
> The vendored version of sqlite, v3.39.4, should be considered to be a security release. From the release notes:
>
> > Version 3.39.4 is a minimal patch against the prior release that addresses issues found since the
> > prior release. In particular, a potential vulnerability in the FTS3 extension has been fixed, so
> > this should be considered a security update.
> >
> > In order to exploit the vulnerability, an attacker must have full SQL access and must be able to
> > construct a corrupt database with over 2GB of FTS3 content. The problem arises from a 32-bit
> > signed integer overflow.
>
> For more information please see [GHSA-mgvv-5mxp-xq67](https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-mgvv-5mxp-xq67).
>
>
>
> ---
>
> sha256:
>
></tr></table>
... (truncated)
</details>
<details>
<summary>Changelog</summary>
*Sourced from [sqlite3's changelog](https://github.com/sparklemotion/sqlite3-ruby/blob/master/CHANGELOG.md).*
> ## 1.5.2 / 2022-10-01
>
> ### Packaging
>
> This version correctly vendors the tarball for sqlite v3.39.4 in the vanilla "ruby" platform gem package, so that users will not require network access at installation.
>
> v1.5.0 and v1.5.1 mistakenly packaged the tarball for sqlite v3.38.5 in the vanilla "ruby" platform gem, resulting in downloading the intended tarball over the network at installation time (or, if the network was not available, failure to install). Note that the precompiled native gems were not affected by this issue. [#352](https://github.com/sparklemotion/sqlite3-ruby/issues/352)
>
>
> ## 1.5.1 / 2022-09-29
>
> ### Dependencies
>
> * Vendored sqlite is updated to [v3.39.4](https://sqlite.org/releaselog/3_39_4.html).
>
> ### Security
>
> The vendored version of sqlite, v3.39.4, should be considered to be a security release. From the release notes:
>
> > Version 3.39.4 is a minimal patch against the prior release that addresses issues found since the
> > prior release. In particular, a potential vulnerability in the FTS3 extension has been fixed, so
> > this should be considered a security update.
> >
> > In order to exploit the vulnerability, an attacker must have full SQL access and must be able to
> > construct a corrupt database with over 2GB of FTS3 content. The problem arises from a 32-bit
> > signed integer overflow.
>
> For more information please see [GHSA-mgvv-5mxp-xq67](https://github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-mgvv-5mxp-xq67).
>
>
> ## 1.5.0 / 2022-09-08
>
> ### Packaging
>
> #### Faster, more reliable installation
>
> Native (precompiled) gems are available for Ruby 2.6, 2.7, 3.0, and 3.1 on all these platforms:
>
> - `aarch64-linux`
> - `arm-linux`
> - `arm64-darwin`
> - `x64-mingw32` and `x64-mingw-ucrt`
> - `x86-linux`
> - `x86_64-darwin`
> - `x86_64-linux`
>
> If you are using one of these Ruby versions on one of these platforms, the native gem is the recommended way to install sqlite3-ruby.
>
> See [the README](https://github.com/sparklemotion/sqlite3-ruby#native-gems-recommended) for more information.
>
></tr></table>
... (truncated)
</details>
<details>
<summary>Commits</summary>
- [`5c443e2`](https://github.com/sparklemotion/sqlite3-ruby/commit/5c443e239e204dc6bebb6129d9f7b8be854fed1e) version bump to v1.5.2
- [`5ab9cd8`](https://github.com/sparklemotion/sqlite3-ruby/commit/5ab9cd849fd070b724d8c2b3d0da98c093f88e75) Merge pull request [#352](https://github.com/sparklemotion/sqlite3-ruby/issues/352) from sparklemotion/351-fix-tarball-packaging
- [`d37f248`](https://github.com/sparklemotion/sqlite3-ruby/commit/d37f248548e6c3fdbacd3d8681a3f9ffbe4bb1cb) fix: native.rake and test-gem-file-contents use dependencies.yml
- [`df549ed`](https://github.com/sparklemotion/sqlite3-ruby/commit/df549ed0f8c9ef33760521d5cd356682685d4209) refactor: extract mini_portile recipe config to dependencies.yml
- [`8ab3ecc`](https://github.com/sparklemotion/sqlite3-ruby/commit/8ab3ecce3857d4ff5a705e8ed6c4680b01930771) version bump to 1.5.1
- [`b026da1`](https://github.com/sparklemotion/sqlite3-ruby/commit/b026da11a1735eae197a9a2f6222a477cca651c1) Merge pull request [#349](https://github.com/sparklemotion/sqlite3-ruby/issues/349) from sparklemotion/flavorjones-update-sqlite-3.39.4
- [`8ebb39d`](https://github.com/sparklemotion/sqlite3-ruby/commit/8ebb39d36483a2f3fd6601ac10a5fae899ce1208) dep: update packaged sqlite3 to v3.39.4
- [`4bf6f66`](https://github.com/sparklemotion/sqlite3-ruby/commit/4bf6f66222696bf2037da1e667c8f385b9322205) doc: clarify how to avoid installing a native gem
- [`31ea008`](https://github.com/sparklemotion/sqlite3-ruby/commit/31ea0084ced0a317fbf2e4c21b2ba3cd2694025b) version bump to 1.5.0 (final)
- [`23721a7`](https://github.com/sparklemotion/sqlite3-ruby/commit/23721a701a878c0d7cd6fdbd2baf883980048827) rb_gc_register_address() must be called after the variable was assigned ([#345](https://github.com/sparklemotion/sqlite3-ruby/issues/345))
- Additional commits viewable in [compare view](https://github.com/sparklemotion/sqlite3-ruby/compare/v1.4.4...v1.5.2)
</details>
<br />https://git.tchncs.de/Illuna-Minetest/illuna-minetest.tk/-/merge_requests/40Bump bootstrap from 4.1.0 to 5.2.12022-09-21T15:03:39+02:00DependabotBump bootstrap from 4.1.0 to 5.2.1Bumps [bootstrap](https://github.com/twbs/bootstrap-rubygem) from 4.1.0 to 5.2.1.
<details>
<summary>Release notes</summary>
*Sourced from [bootstrap's releases](https://github.com/twbs/bootstrap-rubygem/releases).*
> ## v5.0.0
> No re...Bumps [bootstrap](https://github.com/twbs/bootstrap-rubygem) from 4.1.0 to 5.2.1.
<details>
<summary>Release notes</summary>
*Sourced from [bootstrap's releases](https://github.com/twbs/bootstrap-rubygem/releases).*
> ## v5.0.0
> No release notes provided.
>
> ## v4.2.1
> * Bootstrap rubygem now depends on SassC instead of Sass.
</details>
<details>
<summary>Changelog</summary>
*Sourced from [bootstrap's changelog](https://github.com/twbs/bootstrap-rubygem/blob/main/CHANGELOG.md).*
> # Changelog
>
> The changelog is tracked here but also in [the Releases section of the GitHub project](https://github.com/twbs/bootstrap-rubygem/releases).
> The changelog only includes changes specific to the RubyGem.
>
> The Bootstrap framework changes can be found in [the Releases section of twbs/bootstrap](https://github.com/twbs/bootstrap/releases).
> Release announcement posts on [the official Bootstrap blog](http://blog.getbootstrap.com) contain summaries of the most noteworthy changes made in each release of Bootstrap.
>
> # 4.2.1
>
> * Bootstrap rubygem now depends on SassC instead of Sass.
>
> # 4.0.0.beta2.1
>
> Fixes an extraneous `sourceMappingURL` in `bootstrap.js`.
> [#124](https://github.com/twbs/bootstrap-rubygem/issues/124)
>
> # 4.0.0.beta2
>
> Compass is no longer supported. Minimum required Sass version is now v3.5.2.
> [#122](https://github.com/twbs/bootstrap-rubygem/pull/122)
>
> # 4.0.0.alpha3.1
>
> This release corresponds to the upstream Bootstrap 4 Alpha 3.
</details>
<details>
<summary>Commits</summary>
- [`6ecce3b`](https://github.com/twbs/bootstrap-rubygem/commit/6ecce3b28ef31d48a7f0e5d1bafb5dfd4812812f) Update to v5.2.1
- [`c548a9a`](https://github.com/twbs/bootstrap-rubygem/commit/c548a9a69cc1d4b833696722666c1c610cf9f4a0) tasks/updater/js.rb: Fix popper reference
- [`49a70a4`](https://github.com/twbs/bootstrap-rubygem/commit/49a70a4933a1e3dbf8ec06e29fc2ed170f25ccd7) Add Importmaps section to README
- [`003c627`](https://github.com/twbs/bootstrap-rubygem/commit/003c627ea7589dbbd8aeff030353b8c5decb6fbf) Update to v5.2.0
- [`badd3ae`](https://github.com/twbs/bootstrap-rubygem/commit/badd3aed1ad8e7659485865687412ad3a27ff6a3) Prepare for v5.2.0
- [`9892831`](https://github.com/twbs/bootstrap-rubygem/commit/9892831e005bdb2da72f41aa42a6391baa6ad188) Update to v5.1.3
- [`dcf74d7`](https://github.com/twbs/bootstrap-rubygem/commit/dcf74d7daa8c8c7f7e6705e3761fbf0836161183) Update to v5.1.2
- [`9b7f652`](https://github.com/twbs/bootstrap-rubygem/commit/9b7f652f18a43afde55ac3996f7ede6c95d86dc7) Update to v5.1.1
- [`8180cf0`](https://github.com/twbs/bootstrap-rubygem/commit/8180cf0f5e6c11cd2bbe31528fbce0243157dcc8) Update to v5.1.0
- [`4c1cc4a`](https://github.com/twbs/bootstrap-rubygem/commit/4c1cc4a2bc023dfb50d8d16f70ff00254fa33957) Update JS updater for v5.1.0
- Additional commits viewable in [compare view](https://github.com/twbs/bootstrap-rubygem/compare/v4.1.0...v5.2.1)
</details>
<br />https://git.tchncs.de/Illuna-Minetest/illuna-minetest.tk/-/merge_requests/38Bump puma from 5.6.4 to 5.6.52022-08-31T15:04:33+02:00DependabotBump puma from 5.6.4 to 5.6.5Bumps [puma](https://github.com/puma/puma) from 5.6.4 to 5.6.5.
<details>
<summary>Release notes</summary>
*Sourced from [puma's releases](https://github.com/puma/puma/releases).*
> ## 5.6.5 / 2022-08-23
>
> * Bugfixes
> * NullIO#cl...Bumps [puma](https://github.com/puma/puma) from 5.6.4 to 5.6.5.
<details>
<summary>Release notes</summary>
*Sourced from [puma's releases](https://github.com/puma/puma/releases).*
> ## 5.6.5 / 2022-08-23
>
> * Bugfixes
> * NullIO#closed should return false ([#2883](https://github.com/puma/puma/issues/2883))
> * Puma::ControlCLI - allow refork command to be sent as a request ([#2868](https://github.com/puma/puma/issues/2868), [#2866](https://github.com/puma/puma/issues/2866))
> * [jruby] Fix TLS verification hang ([#2890](https://github.com/puma/puma/issues/2890), [#2729](https://github.com/puma/puma/issues/2729))
> * extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used ([#2885](https://github.com/puma/puma/issues/2885), [#2839](https://github.com/puma/puma/issues/2839))
> * MiniSSL - detect SSL_CTX_set_dh_auto ([#2864](https://github.com/puma/puma/issues/2864), [#2863](https://github.com/puma/puma/issues/2863))
> * Fix rack.after_reply exceptions breaking connections ([#2861](https://github.com/puma/puma/issues/2861), [#2856](https://github.com/puma/puma/issues/2856))
> * Escape SSL cert and filenames ([#2855](https://github.com/puma/puma/issues/2855))
> * Fail hard if SSL certs or keys are invalid ([#2848](https://github.com/puma/puma/issues/2848))
> * Fail hard if SSL certs or keys cannot be read by user ([#2847](https://github.com/puma/puma/issues/2847))
> * Fix build with Opaque DH in LibreSSL 3.5. ([#2838](https://github.com/puma/puma/issues/2838))
> * Pre-existing socket file removed when TERM is issued after USR2 (if puma is running in cluster mode) ([#2817](https://github.com/puma/puma/issues/2817))
> * Fix Puma::StateFile#load incompatibility ([#2810](https://github.com/puma/puma/issues/2810))
</details>
<details>
<summary>Changelog</summary>
*Sourced from [puma's changelog](https://github.com/puma/puma/blob/master/History.md).*
> ## 5.6.5 / 2022-08-23
>
> * Feature
> * Puma::ControlCLI - allow refork command to be sent as a request ([#2868](https://github.com/puma/puma/issues/2868), [#2866](https://github.com/puma/puma/issues/2866))
>
> * Bugfixes
> * NullIO#closed should return false ([#2883](https://github.com/puma/puma/issues/2883))
> * [jruby] Fix TLS verification hang ([#2890](https://github.com/puma/puma/issues/2890), [#2729](https://github.com/puma/puma/issues/2729))
> * extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used ([#2885](https://github.com/puma/puma/issues/2885), [#2839](https://github.com/puma/puma/issues/2839))
> * MiniSSL - detect SSL_CTX_set_dh_auto ([#2864](https://github.com/puma/puma/issues/2864), [#2863](https://github.com/puma/puma/issues/2863))
> * Fix rack.after_reply exceptions breaking connections ([#2861](https://github.com/puma/puma/issues/2861), [#2856](https://github.com/puma/puma/issues/2856))
> * Escape SSL cert and filenames ([#2855](https://github.com/puma/puma/issues/2855))
> * Fail hard if SSL certs or keys are invalid ([#2848](https://github.com/puma/puma/issues/2848))
> * Fail hard if SSL certs or keys cannot be read by user ([#2847](https://github.com/puma/puma/issues/2847))
> * Fix build with Opaque DH in LibreSSL 3.5. ([#2838](https://github.com/puma/puma/issues/2838))
> * Pre-existing socket file removed when TERM is issued after USR2 (if puma is running in cluster mode) ([#2817](https://github.com/puma/puma/issues/2817))
> * Fix Puma::StateFile#load incompatibility ([#2810](https://github.com/puma/puma/issues/2810))
</details>
<details>
<summary>Commits</summary>
- [`3bace01`](https://github.com/puma/puma/commit/3bace01d3009dabc6a7ea269b97bdfea455128cb) 5.6.5
- [`3ce6668`](https://github.com/puma/puma/commit/3ce6668093da3e9bf73cbf7bdb107e6eafb3cbac) 5.6.5 release note
- [`0147ac6`](https://github.com/puma/puma/commit/0147ac67d47b6c37e747eac0cdea67a69443086b) Upstream master build changes ([#2913](https://github.com/puma/puma/issues/2913))
- [`0970c91`](https://github.com/puma/puma/commit/0970c91636ea870c1f7c9bb3737671b76f1f068b) test_integration_ssl.rb - fix LogWriter reference
- [`790424c`](https://github.com/puma/puma/commit/790424c8f2ed245b0c51644e6ae3189568708784) Add log_writer instance variable to server.rb
- [`6454710`](https://github.com/puma/puma/commit/6454710f1caa5f2d7cfda60b96f57be5854e5f1b) Puma::ControlCLI - allow refork command to be sent as a request ([#2868](https://github.com/puma/puma/issues/2868))
- [`470df09`](https://github.com/puma/puma/commit/470df09ed82b8639bb6dd349f7c64de146a41069) [fix] TLS verification hang on JRuby ([#2890](https://github.com/puma/puma/issues/2890))
- [`a1489dd`](https://github.com/puma/puma/commit/a1489dd89879ab2e77d41ad7ca9e6f58c464db1b) extconf.rb - don't use pkg_config('openssl') if '--with-openssl-dir' is used ...
- [`6d22d50`](https://github.com/puma/puma/commit/6d22d5015b1e038bde32b8f12dc353c16127068b) MiniSSL - detect SSL_CTX_set_dh_auto ([#2864](https://github.com/puma/puma/issues/2864))
- [`e692887`](https://github.com/puma/puma/commit/e6928872283ad2514a5044f67f550f20bd4f1a12) Fix rack.after_reply exceptions breaking connections ([#2861](https://github.com/puma/puma/issues/2861))
- Additional commits viewable in [compare view](https://github.com/puma/puma/compare/v5.6.4...v5.6.5)
</details>
<br />https://git.tchncs.de/Illuna-Minetest/illuna-minetest.tk/-/merge_requests/37Bump pg from 1.4.1 to 1.4.32022-08-31T15:04:11+02:00DependabotBump pg from 1.4.1 to 1.4.3Bumps [pg](https://github.com/ged/ruby-pg) from 1.4.1 to 1.4.3.
<details>
<summary>Changelog</summary>
*Sourced from [pg's changelog](https://github.com/ged/ruby-pg/blob/master/History.rdoc).*
> == v1.4.3 [2022-08-09] Lars Kanis <lars@...Bumps [pg](https://github.com/ged/ruby-pg) from 1.4.1 to 1.4.3.
<details>
<summary>Changelog</summary>
*Sourced from [pg's changelog](https://github.com/ged/ruby-pg/blob/master/History.rdoc).*
> == v1.4.3 [2022-08-09] Lars Kanis <lars@greiz-reinsdorf.de>
>
> - Avoid memory bloat possible in put_copy_data in pg-1.4.0 to 1.4.2. [#473](https://github.com/ged/ruby-pg/issues/473)
> - Use Encoding::BINARY for JOHAB, removing some useless code. [#472](https://github.com/ged/ruby-pg/issues/472)
>
>
> == v1.4.2 [2022-07-27] Lars Kanis <lars@greiz-reinsdorf.de>
>
> Bugfixes:
>
> - Properly handle empty host parameter when connecting. [#471](https://github.com/ged/ruby-pg/issues/471)
> - Update Windows fat binary gem to OpenSSL-1.1.1q.
</details>
<details>
<summary>Commits</summary>
- [`441cb1e`](https://github.com/ged/ruby-pg/commit/441cb1ed4b3350441746d7c94d97168980a6183c) Update History for pg-1.4.3
- [`fff03df`](https://github.com/ged/ruby-pg/commit/fff03dfc4f74a883a765adaa9bfb5d5b36b326af) Bump VERSION to 1.4.3
- [`9929ac9`](https://github.com/ged/ruby-pg/commit/9929ac9f3fee17c9f2d9930728a0a303d90a9ac9) Merge pull request [#474](https://github.com/ged/ruby-pg/issues/474) from larskanis/put_copy_data-flushing
- [`54e22bc`](https://github.com/ged/ruby-pg/commit/54e22bc6b464f92652bce9ee96aab8ae17d776a2) Do a blocking flush every 100 calls to put_copy_data
- [`28b73d2`](https://github.com/ged/ruby-pg/commit/28b73d27893e3a7105fb280cf1df088cac175d43) Merge pull request [#472](https://github.com/ged/ruby-pg/issues/472) from eregon/treat_johab_encoding_as_binary
- [`c9284ff`](https://github.com/ged/ruby-pg/commit/c9284ffc4c911dc060e66fccf70c20e7ddc9eba5) Use Encoding::BINARY for JOHAB
- [`fc939f5`](https://github.com/ged/ruby-pg/commit/fc939f5e015778098d9a67d40ffd50f853e1321f) Usage of environment variables is fixed in Postgres-12
- [`d41fc0c`](https://github.com/ged/ruby-pg/commit/d41fc0cf1e7abac4be95348cf0da9ab0c08ef986) Update Windows fat binary gem to OpenSSL-1.1.1q
- [`757226c`](https://github.com/ged/ruby-pg/commit/757226c61c8f3281a5e83d7829856115ed81edcc) Bump VERSION to 1.4.2 and add release notes
- [`ce85904`](https://github.com/ged/ruby-pg/commit/ce85904672c901bc72e48e8e20cccd3392cfb75c) Make SSL connections independent from files in ~/.postgresql
- Additional commits viewable in [compare view](https://github.com/ged/ruby-pg/compare/v1.4.1...v1.4.3)
</details>
<br />