Skip to content

Conversation

@erikaxel
Copy link
Contributor

@erikaxel erikaxel commented Sep 8, 2025

🤔 What's changed?

The initial warning was from 16 years ago from a bug report that no longer exists, for Rails 2 and is no longer relevant.
This fixed #597

⚡️ What's your motivation?

Removes unnecessary noise.

🏷️ What kind of change is this?

  • 🐛 Bug fix (non-breaking change which fixes a defect)

📋 Checklist:

…lse`

The initial warning was from 16 years ago from a bug report that no longer exists, for Rails 2 and is no longer relevant.
Copy link
Contributor

@luke-hill luke-hill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now this will live in an approved PR. I need to have a think about versioning in the v4 lifecycle.

You don't need to do anything more.

@luke-hill luke-hill merged commit 004ef13 into cucumber:main Oct 14, 2025
10 checks passed
@luke-hill
Copy link
Contributor

I'm going to put this into a patch release, as you've mentioned, this is only a warning so it's purely spam (if nothing else).

I won't release just yet as I'll see any other stuff if it can go in e.t.c. - But I'll cut something before the year is out either way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove the warning about config.cache_classes set to false?

2 participants