wintercms / wintercms/wn-user-plugin
Downgrading instead of Upgrading
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 13
- Forks
- 20
- Avg merge
- 50m
- Merged PRs (30d)
- 1
Description
I start the update
composer update
Result
Then
php artisan winter:up
Result
Then
composer update
Result
Then
php artisan winter:up
Result
So it repeats endlessly.
This came up a few months ago.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the documented sequence of composer update and php artisan winter:up, comparing the dependency and migration results shown in the screenshots. Done means the update process no longer repeatedly alternates between versions after those commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100