Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

create:theme --tailwind scaffolds version.yaml at 1.0.0 while the LESS variant scaffolds 1.0.1

Open Beginner friendly
#1,573 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
laravel, php, tailwindcss, yaml
Domain
cli, tooling

Research direction

Compare modules/cms/console/scaffold/theme/less/version.stub with modules/cms/console/scaffold/theme/tailwind/version.stub and determine the intended initial version. Update the inconsistent stub, then run php artisan create:theme --less and php artisan create:theme --tailwind and confirm both generate matching version.yaml content.

Written by the indexing model from the issue text.

Description

Description

modules/cms/console/scaffold/theme/less/version.stub scaffolds:

1.0.1: 'Initial version'

while modules/cms/console/scaffold/theme/tailwind/version.stub scaffolds:

1.0.0: 'Initial version'

So a site created with create:theme --tailwind starts one patch version behind the LESS variant, for the same initial content.

Reproduction

php artisan create:theme --less   # version.yaml -> 1.0.1
php artisan create:theme --tailwind  # version.yaml -> 1.0.0

Suggested fix

Align the two stubs to the same starting version (likely 1.0.0 for both, or 1.0.1 for both).

Notes

Verified still open as of 2026-10-05 and 2026-10-17. No existing issue found (four searches). Reported from the Winter CMS development workspace.

Dominant language
PHP
Stars
1.5k
Forks
251
Avg merge
2d 16h
Merged PRs (30d)
10

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wintercms/winter

All issues in wintercms/winter

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.