Update blind_index: 2.2.0 → 2.3.1 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ blind_index (2.2.0 → 2.3.1) · Repo · Changelog

Release Notes

2.3.1 (from changelog)

• Fixed error with backfill when bidx_attribute is a symbol

2.3.0 (from changelog)

• Added blind indexes to filter_attributes
• Dropped support for Ruby < 2.6 and Rails < 5.2

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 32 commits:

• Version bump to 2.3.1 [skip ci]
• Fixed error with backfill when bidx_attribute is a symbol - fixes #54
• Added Mongoid 8 to CI
• Updated tests for Lockbox 1.0 [skip ci]
• Updated readme [skip ci]
• Fixed CI
• Updated for Lockbox 1.0
• Added test for model schema loading [skip ci]
• Version bump to 2.3.0 [skip ci]
• Dropped support for Ruby < 2.6 and Rails < 5.2
• Moved require [skip ci]
• Test with Ruby 3.1 on CI
• Use stub method
• Test with Active Record 7 by default
• Test with Active Record 7 rc1
• Test with Active Record 7
• Switched to Lockbox for most tests
• Removed unneeded gem from tests [skip ci]
• Moved development dependencies out of gemspec
• Use ActiveRecord::Schema.define for test setup [skip ci]
• Added index to Mongoid instructions [skip ci]
• Added comment [skip ci]
• Updated changelog [skip ci]
• Merge pull request #51 from soartec-lab/feature/add-active-record-filter-attributes
• Add the column specified in `blind_index` to` filter_attributes`.
• Test with Ruby 3
• Test with Active Record 6.1 by default
• Removed unneeded line [skip ci]
• Fixed test warnings [skip ci]
• Less verbose test output
• Moved to GitHub Actions
• Test with Rails 6.1 [skip ci]

↗️ argon2-kdf (indirect, 0.1.3 → 0.1.7) · Repo · Changelog

Release Notes

0.1.7 (from changelog)

• Improved ARM detection

0.1.6 (from changelog)

• Added ARM shared library for Linux

0.1.5 (from changelog)

• Fixed ARM detection

0.1.4 (from changelog)

• Added ARM shared library for Mac

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

• Version bump to 0.1.7 [skip ci]
• Improve ARM detection for M1 chip on macOS 12.1 (#6)
• Updated gemspec [skip ci]
• Version bump to 0.1.6 [skip ci]
• Added ARM shared library for Linux - #5
• Added vendor:platform task
• Added hashes to vendor tasks
• Version bump to 0.1.5 [skip ci]
• Fixed ARM detection - fixes #4
• Test with Ruby 3, and moved development dependencies out of gemspec
• Version bump to 0.1.4 [skip ci]
• Added ARM shared library for Mac
• Revert "Added arm64 shared library for Mac - #3"
• Added arm64 shared library for Mac - #3
• Moved to GitHub Actions
• Test empty string

↗️ zeitwerk (indirect, 2.6.1 → 2.6.6) · Repo · Changelog

Release Notes

2.6.6 (from changelog)

• The new eager_load_namespace had a bug when eager loading certain namespaces with collapsed directories. This has been fixed.

2.6.5 (from changelog)

• Controlled errors in a couple of situations:

  • Attempting to eager load or reload without previously invoking setup now raises Zeitwerk::SetupRequired.

  • The method Zeitwerk::Loader#push_dir raises Zeitwerk::Error if it gets an anonymous custom namespace.

  These should be backwards compatible, because they raise in circumstances that didn't work anyway. The goal here is to provide a meaningful error upfront.

• Enforcement of private interfaces continues with another gradual patch.

2.6.4 (from changelog)

Ruby does not have gem-level visibility, so sometimes you need things to be public for them to be accessible internally. But they do not belong to the public interface of the gem.

A method that is undocumented and marked as @private in the source code is clearly private API, regardless of its formal Ruby visibility.

This release starts a series of gradual patches in which private interface is enforced with stricter formal visibility.

2.6.3 (from changelog)

• v2.6.2 introduced a regression in the logic that checks whether two loaders want to manage the same root directories. It has been fixed.

2.6.2 (from changelog)

• Zeitwerk::Loader#load_file allows you to load an individual Ruby file. Check its documentation for details.

• Zeitwerk::Loader#eager_load_dir allows you to eager load a directory, recursively. Check its documentation for details.

• Zeitwerk::Loader#eager_load_namespace allows you to eager a namespace, recursively. Namespaces are global, this method loads only what the receiver manages from that namespace, if anything. Check its documentation for details.

• Zeitwerk::Loader.eager_load_namespace broadcasts eager_load_namespace to all registered loaders. Check its documentation for details.

• Documents shadowed files. They always existed, but were not covered by the documentation.

• Other assorted documentation improvements.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #449.