Recommended process to updating between versions
Hi,
Is there a recommended path to updating in between version releases?
Like if I'm using Metronic 9.3.8 via a NextJs app, what is the best way to update to version 9.4.0?
I'm looking for a process to make sure I cover all of the core files that are changed/added/removed with each incremental release.
Thank you!
Replies (7)
Hi Charles,
Thank you for the kind words and for taking the time to share your feedback, we really appreciate it.
We’re glad the steps were useful, and we’ll look into including this update process in the official docs so others can follow it easily. We’ve also released fixes in the KTUI packages for both the HTML and Next.js variants, so you should be in good shape when updating.
Thanks again for your support and for choosing Metronic. If you run into anything else while updating, feel free to ask.
Best,
Your Support Matters!
Awesome! Thanks for all of your hard work and consistent updates! I left a review on Themeforest and if there's anything else I can do to help then feel free to let me know. Thanks!!
Thanks again for your support and for choosing Metronic. If you run into anything else, feel free to ask.
Hi
CSS and theme assets are part of the full Metronic package, not only of the npm dependencies.
1. Update dependencies
Bump Metronic-related versions in package.json and run install
2. Get the new package
Download the v9.4.0 (or target version) package from your KeenThemes account.
3. Bring over updated CSS and assets
From the new package, use the same variant you’re using (e.g. Next.js TypeScript starter):
Styles: Copy or merge the contents of the new version’s styles/ folder (e.g. app/globals.css and any theme/plugin CSS) into your project. If you’ve customised these files, diff and merge instead of overwriting.
Metronic assets: Do the same for any public/ (or equivalent) folders that contain theme assets (icons, images, fonts, etc.) that Metronic expects. Replace or merge as needed, keeping your own custom assets.
4. Use the changelog
Check Metronic Changelog for the versions you’re jumping (e.g. 9.3.8 → 9.4.0). If it mentions “styles”, “CSS”, “components”, or “assets”, those are the areas to compare and update.
There’s no automated “patch only what changed” for your repo; the recommended process is to re-base from the new version’s starter/concept (same type as your app) and then reapply your customisations, or to manually diff and merge the styles/ and relevant asset folders from the new package into your project.
Thanks
Hi Faizal,
Thanks for your reply, that's very helpful! I will save your post, but I think it might be a good idea to include these steps somewhere in the official docs. With the consistent updates that Metronic receives (which is awesome!), I think this information will be very helpful to others.
Thank you again and keep up the great work!! Metronic is #1!
Hi,
Migrating from Metronic v9.3.8 to Metronic v9.4.0 would require updating the package.json and just getting the new starter kits and concepts apps from v9.4.0 package.There is no other breaking changes. You can refer to what is added: https://keenthemes.com/metronic/changelog
Regards,
Sean
Hey Sean, thanks for the response. Your suggestion makes sense for updating public plugins/packages but what about when changes are made to the CSS files or any other Metronic specific assets?
