Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update shoulda-matchers 4.4.1 → 6.1.0 (major) #1074

Closed
wants to merge 2 commits into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 24, 2024

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?

✳️ shoulda-matchers (4.4.1 → 6.1.0) · Repo · Changelog

Release Notes

6.1.0

6.1.0 - 2024-01-19

Bug fixes

Features

  • Add support for negated matcher on have_secure_password matcher by @amalrik (#1593)
  • Add encrypt matcher to test usage of the encrypts macro by @theforestvn88 (#1581)
  • Add query_constraints qualifier on the association matchers by @matsales28 (#1604)

Improvements

6.0.0

Backward-incompatible changes

  • Drop support for Rails 5.2 and 6.0 as well as Ruby 2.6 and 2.7 they've been end-of-lifed by @dougmrqs and @HeitorMC.
    The gem now supports Ruby 3.0+ and Rails 6.1+. (#1521, #1522, #1547, #1548)

Bug fixes

  • Fix validate_uniqueness_of matcher not supporting column of the type timestampz by @callahat. (#1544)
  • Ensure that validation specs work for ActiveModel without ActiveRecord by @stonefield. (#1580)

Features

Improvements

  • When an unrelated error is seen with negated allow_value, give a hint by @matsales28. (#1570)

Thanks everyone for the contributions!

5.3.0

Features

  • Add in: range matcher to validate_numericality_of by @matsales28 . (#1512)

  • Support :uuid column type for validate_absence_of matcher by @dlupu. (#1518)

Bug fixes

  • Fix confusing error message from validate_inclusion_of matcher when used against a polymorphic association. (#1523)

5.2.0

Features

  • Add without_scopes method to enum matcher. (#1453)

  • Add support for Ruby 3.1. (#1474)

  • Add allow_blank method to validate_presence_of matcher. (#1499)

  • Add support for Rails 7.0. No new Rails 7.0 features are supported, but only existing features that broke with the upgrade. (#1506)

5.1.0

Bug fixes

  • Fix the undefined method error for non rails project due to use of many? - method from ActiveSupport. (#1459)

Features

  • Add array option support for have db column matcher. (#1465)

  • Add enum attributes support for validate_absence_of matcher. (#1464)

5.0.0

Bug fixes

  • Replace in?, method from ActiveSupport, with include? to prevent exception "undefined method in?" on non-Rails app. (#1405)

Features

  • Add support for Rails 6.1. No new Rails 6.1 features are supported, but only
    existing features that broke with the upgrade. (#1418)

  • Add support for RVM (Ruby Version Manager) to setting up local environment. (#1424)

  • Add support for alias in matcher define_enum. (#1419)

  • Add support for Ruby 3.0. (#1406, #1427)

Improvements

  • Remove deprecated warnings emitted on Rails 6.1 in ActiveModel errors. (#1444)

4.5.1

Bug fixes

  • Update belongs_to to work with composite primary keys. (#1396)

4.5.0

Features

  • Add support for has_secure_password custom attributes. (#1356)

Bug fixes

  • Fix bundle exec yard doc replacing pygments.rb with rouge to keep the documentation up to date. (#1343)
  • Fix have_db_column.with_options not raising an error when the user adds an invalid value. (#1358)
  • Fix default value of assossiation_matcher.validate option. It was returning false instead of true. (#1378)
  • Fix validate_absence_of failing for array columns. (#1383)

Improvements

  • Replace all links with http to https. (#1340)
  • Update the links for have_and_belong_to_many, have_many and have_one in the README to redirect the user to where the matcher description starts. (#1348)
  • Drop git ls-files in gemspec to help downstreams maintenance, because they often need to build packages in an environment that does not have git. (#1354)
  • Add comment about no support of validate_uniqueness_of(:item).scoped_to(array). (#1355)
  • Improve error message for assossiation_matcher.with_foreign_key option. (#1376)

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.

↗️ concurrent-ruby (indirect, 1.2.2 → 1.2.3) · Repo · Changelog

Release Notes

1.2.3

What's Changed

New Contributors

Full Changelog: v1.2.2...v1.2.3

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

Commits

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


Depfu Status

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 cancel merge
Cancels automatic merging of this PR
@​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 depfu bot added the depfu label Jan 24, 2024
@suse-tests-fail
Copy link
Collaborator

Prophet reports failure.
https://ci.suse.de/job/scc-RMT-integration-tests/355893/console
If the given link has expired,you can force a Prophet rerun by just deleting this comment.
Failed fast in project rmt on step docker-compose-build-images.
Failed fast in project rmt on step docker-compose-build-images. (Merged 8ba771e into ecf5efb)

@digitaltom
Copy link
Member

This requires Ruby3.

@digitaltom digitaltom closed this Feb 1, 2024
@depfu depfu bot deleted the depfu/update/shoulda-matchers-6.1.0 branch February 1, 2024 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants