14 Replies
Hi @Sven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
To upgrade Wasp to the latest version, you should re-run the installer script. You can do this with the following command:
If you want to install or switch to a specific version of Wasp, you can use:
Replace
x.y.z with the desired version number.
You can check the latest available versions at the Wasp GitHub releases page or by running wasp version, which will also show you instructions for upgrading if a newer version is available CLI Reference.
Currently, there is no built-in wasp upgrade command; upgrading is done via the installer script as described above Make process of updating Wasp nicer.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Migration from 0.15.X to 0.16.X | Wasp
What's new in 0.16.0?
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry, but the knowledge sources provided do not contain information about what to do after completing the migration from Wasp 0.15 to 0.16, nor do they reference the specific migration guide at https://wasp.sh/docs/migration-guides/migrate-from-0-15-to-0-16. Therefore, I can't give you a definitive next step based on the available documentation.
If you have completed all the steps in the migration guide, a general best practice (based on previous migration guides) would be to:
- Test your application thoroughly to ensure everything works as expected.
- Run database migrations if required (e.g., with wasp db migrate-dev).
- Deploy your updated app if you are satisfied with local testing.
However, for any specific post-migration steps or recommendations for 0.16, please refer to the official migration guide or ask for help on the Wasp Discord server, as the current knowledge sources do not cover this migration.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Are you experiencing any errors or issues after completing the migration?
yeah
some type stuff
can you paste the errors here?
you followed the migration guide already, right?
Hello! I'm facing some issues with the migration from 0.15.x to 0.17.x. I have followed the guide from 0.15 -> 0.16 and from 0.16 -> 0.17.
Wasp requires package "typescript" to be version "5.8.2" in package.json
I'm getting the above error, but i fixed it by adding/modifying the following to my package.json file:
"typescript": "5.8.2"
Note that the migration guide does not mention this. I don't mind raising a pr on this to modify it. Just let me know which version (0.16 or 0.17) actually requires this change since i migrated directly to 0.17!
Wohooo @LuzzaMcGuzza, you just became a Waspeteer level 1!
It came with 0.17.X but I thought we had it on migration docs.
I will update this.
There is a PR for this now.
We will re-deply docs once it's merged.
Great, thanks @toticozeni !
Glad to be of help, the change should be up now:
https://wasp.sh/docs/migration-guides/migrate-from-0-16-to-0-17#3-update-your-packagejson
Hi @toticozeni one more thing that I noticed mentioned in the migration notes of 0.15 -> 0.16 but not 0.16 -> 0.17 is the Wasp version bump.
In my case I changed it to the below but I'm not sure if it's actually required to change. If it is, it might be worth mentioning in the notes 🙂
Good catch
We will add that one too
Awesome, glad I can contribute to this project even in the slightest way