1.2.6 – August 4, 2024 – The Resurrection Update
Last updated: 05.08.2024 02:20 CEST
This changelog is still in progress. Please check back later for more information. You can learn a lot about the new update in the significantly revised README.md.
Relivator 1.2.6 (August 4, 2024): The Resurrection Update (Release Notes Article)
Below you can see a static draft copy of 👉 the article from Bleverse Docs website 👈. This copy may be a bit outdated since July 20, 2024. Please refer to that blog post to read the most recent version of the article. Bleverse Docs also has translations of the article into other languages; and will contain even more information about Relivator than this README.md, including notes from all past and future releases. We still working on Bleverse Docs, so it can be broken unintentionally. That's why the draft copy of that article duplicated into current README.md.
🥳 Relivator is Back With Version 1.2.6!
We are excited to announce the release of Relivator 1.2.6! This version marks the end of the "all-in-one" approach as we prepare for a more modular future with Reliverse CLI starting from version 1.3.0. The 1.2.6 release includes significant updates, especially in the developer experience (DX). The README.md has been significantly updated. Moving forward, we will introduce Dev (early-access for sponsors), Canary, Release Candidate (RC), and General Availability (GA) branches for better version management. 1.2.6 will serve as a foundation, helping us transition more smoothly to the release of those 1.3.0's branches.
Major Changes and Improvements
The project now uses next-auth v5, clerk v5 and optionally supports tailwindcss v4. Work has commenced on upgrading from React 18 to React 19. This is the last release that simultaneously supports PostgreSQL/MySQL and NextAuth.js/Clerk database integrations. Please refer to the updated Installation section in the README.md of Relivator for more details.
Migration Guidance
Starting from version 1.3.1, we will provide comprehensive guides for migrating from older versions. The usual migration process involves reviewing commit changes and integrating necessary updates into your custom code. However, due to the extensive changes in versions 1.2.6 and 1.3.0, this method is not feasible. We recommend reinstalling the project and transferring your custom features from the previous version to the new version of starter. Thank you for your understanding!
To make the migration as smooth as possible, it's recommended to create a "cluster" folder in "src" and moving all your custom code there. If needed, you can adjust the paths using the Find and Replace feature in VSCode. This will make it much easier to save and transfer your custom code to Relivator 1.2.6.
Default Database Change
Neon PostgreSQL is now the default database instead of PlanetScale MySQL, as the latter no longer offers a free tier. If you require MySQL, Railway offers a more affordable alternative with a $5 credit without requiring a credit card. Note that this version has been primarily tested with Neon PostgreSQL.
Security and Code Improvements
- Type Safety and Editor Autocomplete: This update enhances type safety and editor autocomplete for Drizzle ORM libraries.
- Prettier Replaced by Biome: Prettier has been removed in favor of Biome. The Prettier config will be removed in the next version from the
src/tempfolder. You can re-add it by running thereliversecommand starting from Relivator 1.3.0.
Reliverse Scripts Transition
Reliverse scripts have moved from the "unknown viability" stage to the "unstable" stage. As always, use them at your own risk and make backups. These scripts are now located in the src/tools/unstable folder. Most scripts require Python to be installed.
For more details on this update, you can read my detailed posts in the Relivator thread on Discord. Start with this message.
Thank You So Much
If anyone have any questions or issues, don't hesitate to contact me, means @blefnk, on Discord or GitHub. For more information about 1.2.6 and 1.3.0, please visit #⭐-relivator chat on the project's Discord server and the GitHub Issues page.
Thank you for your continued support and happy coding with Reliverse Website Builder v0.4.0 and Relivator Next.js Template v1.2.6!
Git Release Notes
Full Changelog: 1.2.5...1.2.6
v1.3.0-canary.0 is now published on GitHub! (v1.3.0@canary release notes are merged with v1.2.6 release notes)
Relivator 1.2.6 has lived its first day 🎉! It has already been liked by many! Thank you all for your feedback! 🙏
I stayed up all night to finally make the 1.2.6 release. The journey to version 1.2.6 was really long and tough. After the release, I took a walk and then went to sleep. This helped me come up with a temporary solution for issues, presented in 1.2.6, related to Turbopack and next-intl. For some reason, I didn't encounter these issues during the last tests, but now they have appeared.
The simplest solution: temporarily downgrade from Next.js 15 (canary.101) to Next.js 14 (latest). So, if you already have 1.2.6, you can do this by running the command: "npx nypm add react@latest react-dom@latest next@latest sharp@latest". However, it's better to install the fresh Relivator update, as you'll encounter several problems if you only run this command.
Please install this new v1.3.0-canary.0 version. This first v1.3.x version (the first Relivator's canary branch version ever!) contains a temporary downgrade to Next.js 14 and React 19, along with some additional improvements. This update also temporarily disables some files that use new React 19 features like useActionState, but these files are not yet complete, so you won't lose anything. This update also fixes the header's UI on small screen widths.
By the way, using React 18 and Next.js 14 will give you a "cleaner" console when using pnpm install, as many libraries have not yet included next/react rc/canary in their peerDependencies. Additionally, if you are using pnpm, which is recommended until the full release of 1.3.0 (bun will then become the default instead), you can play around with the pnpm configuration, which is truly flexible. You can read about it in the pnpm docs article.
