Update spring 4.2.1 → 4.3.0 (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?

✳️ spring (4.2.1 → 4.3.0) · Repo · Changelog

Release Notes

4.3.0 (from changelog)

• Fix reloading issue in Ruby 3.3.
• Fixed compatibility with --enable-frozen-string-literal.
• Add embeded engines to default reload matcher.

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

Commits

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

• Release 4.3.0
• Merge pull request #732 from Shopify/drop_3_1_edge_in_ci
• Remove 3.1 + edge from CI
• Merge pull request #730 from thomasmarshall/fix-restart
• Merge pull request #719 from chaadow/patch-1
• Fix reloading in Ruby 3.3
• Merge pull request #723 from Shopify/booted-load-hook
• Add embedded engine initializers to spring watcher
• Fix compatibility with --frozen-string-literal

---

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)

[yoldas]

@depfu rebase

[yoldas]

Error in console does not show the fix merged in develop after the rebase. Try recreating it.

[yoldas]

@depfu recreate

[yoldas]

Add expectations (URL change) before record counts to avoid flaky behaviour, i.e. capybara will spend default_max_wait_time to check the URL change and then record count will happen. In this case, the URL change means the end of database write so record count should return the correct result.