Skip to content

fix: do not use autoloading for seeder class check - #3

Merged
tiller1010 merged 1 commit into
mainfrom
hotfix/1.0.1/no-autoload-in-seeder-class-check
Jul 9, 2026
Merged

fix: do not use autoloading for seeder class check#3
tiller1010 merged 1 commit into
mainfrom
hotfix/1.0.1/no-autoload-in-seeder-class-check

Conversation

@tiller1010

@tiller1010 tiller1010 commented Jul 8, 2026

Copy link
Copy Markdown
Member

https://werkbotstudios.teamwork.com/app/tasks/39519302

Summary

do not use autoloading for seeder class check

Testing Steps

Issues/Concerns

  • This just fixes an error on dev/build: "Cannot declare class because the name is already in use in". It does not allow the seeder to be used on sites not on 5.3, like the werkbot site, where the psr-4 updates changed class names.

Git Flow

  • DO NOT delete "release/*" or "hotfix/*" branches after merging a PR. These are used to publish the next release, and they are deleted automatically.
  • "Squash and merge" is good on "feature/*" into "develop"
  • "Create a merge commit" is good on "release/*" or "hotfix/*" into "main"

@tiller1010 tiller1010 added the patch Semver - Patch label Jul 8, 2026
@tiller1010
tiller1010 requested a review from aletail July 8, 2026 16:12

@aletail aletail left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good!

@tiller1010
tiller1010 merged commit 7a60e0f into main Jul 9, 2026
3 checks passed
@github-actions
github-actions Bot deleted the hotfix/1.0.1/no-autoload-in-seeder-class-check branch July 9, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

patch Semver - Patch

Development

Successfully merging this pull request may close these issues.

2 participants