Skip to content
Nevela 0.33.1: New: customers get a shop in the mobile app, each sees only their own orders, and an administrator manages people and roles from the phone. Build it in the new drinks-app tutorial.A drinks app on the phone

Changelog

What changed in each version. “Unreleased” lists what is merged but not yet tagged. While the version is below 1.0.0, a minor release may include breaking changes; they are marked Breaking.

Unreleased

Fixed

  • Signing out of the mobile app no longer shows a red error. In an app whose shop is public, every sign-out showed The action 'REMOVE_ROUTES' … was not handled by any navigator in development. The screens now stay while the shop is described again, and the description starts loading in the same moment as the sign-out.

0.33.1 - 2026-11-19

Sign-in with cached routes, and the scheduler without cron

Added

  • Deploying to a container host: the Laravel app on Sevalla, Railway, Fly.io, Render and other hosts that run one container from a start command: a disk that lasts for SQLite and uploads, the queue without a worker, the scheduler without cron (php artisan schedule:work beside the web server), and caching.

Changed

  • “The scheduler isn’t running” says what to do on a host with no cron: run php artisan schedule:work beside the web server. The bell’s notice links to how, and nevela deploy:check puts that first when it runs in a container.

Fixed

  • Sign-in and public routes work with the routes cached. With php artisan route:cache or php artisan optimize, which many hosts run on start, every sign-in failed with Rate limiter [nevela-auth] is not defined and every public route with Target class [nevela.throttle] does not exist, both a 500. The rate limiter and the middleware alias are now set up whether the routes come from the cache or not.

0.33.0 - 2026-11-18

Browsing the shop on the phone before signing in

Added

  • The mobile app’s shop is open before signing in, when what it sells has a public side. Someone who isn’t signed in opens on the shop, browses, searches and opens a product; Add to cart takes them to sign in or make an account, then back to what they were adding. Signed-in screens stay behind sign-in. An app whose catalogue isn’t public opens on signing in, as before. See Let people browse before signing in.
  • GET /api/public/_nevela/resources: what anyone may read, described: only resources with a public.read, each cut to the fields it opens, with the one a shop sells marked "sold": true. Nothing of the order or its lines.

0.32.0 - 2026-11-17

Orders that can’t be edited once placed, and buttons that move them on

Added

  • Records fixed once made: --fixed, or "fixed": true. Once a record is made, nobody signed in edits or deletes it, the administrator included, and its lines can’t be added to, changed or taken away: Laravel answers 409, from the dashboard, the phone, an import or any other address. It moves on only through its actions. The request that makes it can still finish it (its lines, a total in itemsSaved()), and seeders, the console and queued jobs can do anything. A customer can’t choose, when they make one, the values its actions set. The dashboard and the mobile app show no Edit or Delete on one. See Records fixed once made.
  • Actions that only set values: "set": { "status": "accepted" }. Nevela does them, and no class is written. And when takes a list, any of which will do: { "status": ["pending", "accepted"] }. See Moving a status on.
  • A record’s history. Every record action done is kept as a step: what, by whom, when, what it changed and what was filled in for it, never merged. It is on the record’s page in the dashboard and the mobile app, for whoever may see the record, the customer an order belongs to included (GET /api/_nevela/history/{slug}/{id}). And that person is told of each step in the bell: Your order JM-0014 is now Ready, with the reason when one was asked for. A step they take themselves (a customer cancelling) is told to those who may edit the resource instead: Order JM-0014 is now Cancelled, by whom. It needs a migration: php nevela migrate. See A record’s history.
  • Actions in the mobile app. A record’s page has a button for each action the person may take while it applies, asking its question and what it needs (a reason) first, then the record’s history.

Changed

  • The drinks-app tutorial: placed orders are fixed. Orders are made with --fixed and a cancelled status, and move on by buttons: Accept, Start preparing, Ready, Complete, the customer’s Cancel order at any time until it is completed (with a reason if they like; the bar is told), and the bar’s Cancel with a reason. The customer reads the order’s history on the phone and is told of each step.

0.31.2 - 2026-11-17

The activity log and the trash in the mobile app

Added

  • Activity and Trash in the mobile app. Under Account, in a new Keeping track card. Activity is the activity log: who added, changed, deleted, restored or removed which records, newest first, filtered by what was done, for whoever holds activity.view; the home’s Recent activity has a See all that opens it. Trash lists each resource’s deleted records with how long each has left: restore one, remove one for good, or empty a resource’s trash, for whoever may delete something. Laravel decides what each person sees and may do, as in the dashboard. See What is in it.

0.31.1 - 2026-11-17

A cover for the drinks-app tutorial

Added

  • A cover picture for the drinks-app tutorial, on the tutorials page and on its sample post in every new app’s blog.

0.31.0 - 2026-11-17

The mobile app: a shop, people and roles, and a drinks tutorial

Added

  • Sign up from the mobile app. Where the API lets people create their own account, the sign-in screen links to a sign-up screen: a name, an email and a password, and the code that was emailed where the API asks for the address to be proved first. A request that timed out after making the account offers to sign in instead, with the address filled in.
  • Google (and GitHub) sign-in from the mobile app. The sign-in and sign-up screens show Continue with Google where the API has it switched on. The API has a way back of its own for apps, GET /api/auth/oauth/{provider}/app, which asks Google who the person is and hands the browser to the app’s address with only the state; the app proves it is the one that began the sign-in with a secret it keeps, so nothing taken off the phone signs anybody in. It needs the API’s APP_URL address registered with Google beside the dashboard’s, and the apps it may send people to listed in the new auth.social.app_redirects setting (NEVELA_APP_REDIRECTS). nevela new my-app --mobile sets it. See From the mobile app.
  • An app for customers. The API’s auth config now says which role someone who signs up starts with (defaultRole), and that role can be set with NEVELA_DEFAULT_ROLE. The mobile app gives an account that holds only that role a customer home, listing what they may browse, and no Records tab. Staff and administrators keep the app they had. See Customers and staff.
  • A shop on the phone. When the app has an order resource with lines and a catalogue, a customer’s home is a shop: a grid with search, categories and availability, a product screen, a cart kept on the phone for each account, checkout that places the order with its lines in one request, and an Orders tab where each order shows its status as a trail. Laravel works out the number, prices and total. It is found from the resources; site.shop in lib/site.ts adjusts it. See A shop on the phone, which also gives the model recipe that keeps customers to their own orders.
  • Records that belong to their maker: "owner" in a descriptor. "owner": "email" names the string field that holds whose record it is. Each person sees only their own records (the list, counts, a record’s page, the trash, the bell), a record they make is made theirs whatever the request said, and anyone who may edit the resource sees them all. nevela:generate adds the Owned trait to the model. The mobile shop uses it so each customer sees only their own orders, and doesn’t ask for the field. See Which records each person sees.
  • People, and Roles and permissions, in the mobile app. Under Account, for whoever may view users or roles: search the people who can sign in, add one, change their name, email, password and roles, switch their sign-in off, sign them out everywhere or remove them; and make, edit and delete roles with a switch for each thing a role may do to each part of the app, resource actions included. The same rules as the dashboard, kept by Laravel. See People and roles.
  • The mobile app no longer says passkeys are managed from it. Its settings row reads “Two-step sign-in”. Listing and removing passkeys stays on that screen; adding one and signing in with one are not in the app yet.
  • nevela resource --owner=email, the same setting from the command line. The owner field may be left out of a request (Laravel fills it), and staff who make a record without one own it.
  • A seventh tutorial: A drinks app on the phone. A beverage ordering app for a campus juice bar, built from an empty folder with nevela new juice-me --mobile: customers sign up on their phones, order and follow their order; staff move it along. CI builds it in a new app, checks what each person orders and sees, and checks the mobile app finds its shop in the resources. A tutorial may now say in examples/<name>/new-args what nevela new should be given.
  • GET /_nevela/resources carries the app’s currency (NEVELA_CURRENCY) on money fields that have none of their own, so the phone formats money as the dashboard does.

Changed

  • Money in the mobile app is formatted as in the dashboard: the currency’s symbol and its own number of decimals (none for UGX).
  • In the mobile app, an account that holds only the sign-up role now gets the customer app. That includes accounts that existed before this, such as the ten sample users, which hold only USER. They lose the staff home and the Records tab, and keep everything the dashboard gives them. Give an account another role to keep the staff app.
  • The mobile app’s home says so when an account has been given nothing, instead of showing the command for adding a resource to someone who can’t run it.

Fixed

  • A line’s quantity has to be at least one. The lines of an order (quantity or qty) were checked to be a whole number, so a line of minus two could be sent over the API and take money off the order’s total. Run nevela generate to have your lines refuse it. A stock quantity on an ordinary resource is unchanged.
  • The mobile app’s password boxes had no way to show what was typed. Signing in, changing a password and the two-step setup all asked for a password with no eye to uncover it, which is hard to get right on a small keyboard. Each password box now has one.

0.30.0 - 2026-11-16

A mobile app for iOS and Android, from one flag

Added

  • A mobile app: nevela new my-app --mobile. It adds apps/mobile beside the API and the dashboard: an Expo app for iOS and Android, named for your app. It signs in to the same API with the same accounts, by password or an emailed code, with the second step for an account that has one. Home is the dashboard’s bell, Account changes your name and password, and Settings lists the devices you are signed in on and signs them out. The tokens are kept in the phone’s keychain and renewed by themselves. nevela upgrade leaves apps/mobile alone for now. See The mobile app.
  • The mobile app’s home shows how the app is doing. A card per resource with its total, this week’s new ones against last week’s and a chart of the last 30 days, a button to add each kind of record, the latest changes from the activity log, and the bell with its count. Every figure comes from the API with the person’s own permissions. The tab bar floats above the content.
  • Pictures and your profile picture from the phone. Image fields and galleries in a record’s form take a photo from the camera or the library, sent as soon as it is chosen; Laravel optimises it as it does for the dashboard. Account changes your profile picture the same way.
  • Two-step sign-in from the phone. Turn it on with an authenticator app (open the one on the phone, scan a QR code, or copy the setup key) or with codes by email, keep the backup codes, make new ones or turn it off. Passkeys are listed and can be removed; adding one stays in the dashboard. Settings also chooses light, dark or the phone’s appearance.
  • The mobile app shows your resources, with nothing to generate. Its Records tab lists every resource your role may view. Each has a list with search, a page per record, and forms to create and change one: a control per field, a search of the other resource for a belongsTo, a list for an enum, and Laravel’s complaint about a field shown under it. The screens are drawn from what the API says the resources are, so a resource or a field added later shows up without regenerating or rebuilding the app. Editing line items and files that aren’t pictures stay in the dashboard for now. See Your resources.
  • nevela dev serves the API to your network when the project has a mobile app, so a phone on the same Wi-Fi can reach it, and says so when it starts. It also writes the API’s port to apps/mobile/.env.local, so the app still finds the API when port 8000 was taken. A project without apps/mobile is served on 127.0.0.1 as before. The new mobile_path setting (NEVELA_MOBILE_PATH) says where the app is; empty turns this off.

Changed

  • nevela new shows what it is making, line by line. Before, three lines covered the whole install, and the longest sat still for a minute or more. Now each thing has its own line with what it made and how long it took: the project folder, the dashboard, the Laravel app, its packages, the environment, the database, the administrator, the sample users, the blog, the dashboard’s packages and the git repository. The line in hand moves: a spinner, the time so far, and what it is on, such as 37/119 symfony/console while packages land or the table a migration is creating. In a log or CI, where nothing can be redrawn, each step is one finished line.

0.29.2 - 2026-11-14

Two people editing the same order no longer lose each other’s lines

Fixed

  • Two people editing the same order: a save could replace the other person’s lines without showing them. When someone else saved a record with lines while you had it open, the form kept the lines you had loaded, and your next save put them in place of theirs. The 409 now carries the record’s lines (current.items). If only they changed the lines, theirs come into the form. If you both did, yours stay, nothing is saved, and the notice has a Use their lines button. See Two people editing the same record.

0.29.1 - 2026-11-05

Clearer sidebar separation, and two people editing at once

Added

  • Two people editing the same record no longer undo each other. The edit form sends back the updatedAt it read. If someone else has saved since, Laravel refuses the change and sends the record as it is now. The form then fits the two together field by field. When none of your fields clash with theirs, it saves again by itself and says what they changed. When you both changed a field, yours stays with theirs beneath it and a Use theirs link, and nothing is saved until you save again. See Two people editing the same record.

Changed

  • System-provided resources now have clear visual separation in the sidebar. The Blog section (and other grouped resources) appear below user-created resources with a border separator and muted label color, making it obvious which resources came with the app versus which were created with nevela resource. Before, they appeared mixed together with no visual distinction.
  • A PATCH or PUT that sends updatedAt is now held to it. Before, updatedAt was ignored. Now, if someone saved the record after that time, the answer is a 409 with code: "CHANGED_SINCE_READ" and the record as it is now, and nothing is changed. Leave updatedAt out to save regardless. A client that echoes back a whole record it read earlier will now see this 409 instead of overwriting newer changes. Breaking for such a client. See When someone else saved first.

0.29.0 - 2026-11-02

A CRM tutorial, four field types, real phone numbers, resumable seeds

Added

  • A sixth tutorial: a CRM, the app of Grit’s CRM tutorial: companies and a million contacts, with phone numbers from any country, emails, domains, colours, times, percentages and ratings kept one way, and a seed you can stop and run again. A table says what each of Grit’s commands is here. CI builds it in a new app, with fewer contacts, and it is a post in each new app’s blog.
  • NEVELA_PHONE_COUNTRY says where a phone number without a + is from: with UG, 0772 123456 in a tel field is +256772123456, and the dashboard’s picker starts at Uganda. See Phone numbers.
  • tel(GB), tel(US) and every other country’s code. tel(XX) knew Uganda, Kenya, Tanzania and Rwanda; it now knows 245 countries.
  • Four more field types. domain keeps a bare host in small letters, so a pasted https://Example.COM/about is example.com, and an international name as punycode. country is a searchable list of 249 countries, with their flags where the system draws them (Windows shows the letters), kept as UG, and country(UG), or Grit’s country:country:UG, makes that its default. time is a time of day, kept as 09:05. json is an object or a list, edited as JSON. Each has its input, its checks and its seed data. See Types.
  • A rating can be out of more than five: stars:rating(10), or Grit’s stars:rating:10, gives ten stars, and anything from 2 to 10.
  • More of Grit’s spellings in --fields: select[…] and radio[…] for an enum, quoted labels such as net15="Net 15", toggle and checkbox for a boolean, and textarea for text. See Coming from Grit or Flare.

Changed

  • nevela seed --count is how many the table should hold, as in Grit, and not how many to add. It seeds what is missing, and run again it says so and does nothing. Breaking: a script that runs nevela seed Product --count=100 twice to get 200 now gets 100.
  • A seed can be stopped and run again. Rows are saved 5,000 at a time, so stopping loses at most that many, and the same command carries on to exactly the number asked for. Only --fresh is still all or nothing. Seeded unique values now go on from what the table holds, in place of a large random number.
  • A tel field holds a real phone number. It took anything up to 32 characters: blue, or +256 12. It is now checked against libphonenumber, as the dashboard’s input already was, and kept as +256772123456, so two ways of writing a number are one number to a unique field. Breaking: a number without a + is refused unless NEVELA_PHONE_COUNTRY is set, and a record whose saved number isn’t real is refused the next time a change sends it. Records keep what they have until then. Run nevela generate, which nevela upgrade does for you. This adds giggsey/libphonenumber-for-php-lite to nevela/laravel, about 3 MB.
  • Emails and colours are kept in one form. Ada@Example.COM is saved as ada@example.com, so a unique email can’t be taken twice by writing it differently. #ABC and #ABCDEF are saved as #aabbcc and #abcdef. Records already saved keep what they have until they are next saved, so a table can still hold an address in capitals beside the same one in small letters.
  • A url field takes http and https only. ftp:// and the like were accepted, and shown as a link. Breaking for a field that holds other kinds on purpose: use a string.
  • A rating is from 1 to its most. 0 and 99 were accepted, and shown as no stars and too many. An optional one can still be empty. Breaking for a rating that holds 0 on purpose: a record that has one is refused the next time a change sends it.

Run nevela generate, which nevela upgrade does for you.

Fixed

  • An action’s input is held to what a resource’s is: a url to http and https, and a rating to its range.
  • :unique after a type made nothing unique. email:email:unique was accepted and the field wasn’t unique, with no word about it, and phone:tel:UG:unique was refused. Both now mean what they say, as email:email! and phone:tel(UG)! do. A resource already made that way isn’t changed: to make the field unique, add "unique": true to it in the descriptor and write a migration for the index.
  • Anything else after a type is refused. rating:rating:10 or email:email(work) used to lose the part after the type, and now says so. Descriptors already written aren’t affected.
  • A unique text is refused, with what to use instead. body:text! wrote a migration that fails on MySQL, which can’t index a whole text column. body:string! is unique everywhere. A descriptor that already says so is still read.

0.28.1 - 2026-11-01

A boolean left out is false, and seeded numbers that follow on

Fixed

  • Seeding a table that already has records goes on from the last number given. A second nevela seed gave a numbered field numbers such as ORD-1180000006, and every order made after that followed on from it. Now it is ORD-0021, and the next order ORD-0022. A table that already has such numbers goes on from the highest; nevela seed --fresh starts again. The numbers a seed uses are spoken for as it starts, so none is given again after being removed for good, and a slug made from a number is made from that one.
  • Something typed in that starts like a number no longer hides the highest. Fifty or more records with a longer value such as ORD-2026-0001 made the next number start again from ORD-0001.
  • A boolean left out is false. sent:boolean was required over the API, in an import and in a bulk create, though the form always sends its switch: leaving it out answered 422, “The sent field is required.” It now means no, as =false would say, and null is still refused. A PUT that leaves it out sets it to false, as a PUT does with any default, where before it was refused; a PATCH leaves it as it was. Run nevela generate, which nevela upgrade does for you.
  • A default counts when fields go together once only. With --unique=room,tier and tier:enum(a|b)=a, a record that left tier out wasn’t checked against the set, so the second such record answered 409 without saying which fields clash. It now answers 422 with the usual message, and a bulk create says which row it is the same as.

0.28.0 - 2026-11-01

An invoice tutorial, nevela field, safe numbering and a Print button

Added

  • A fifth tutorial: an invoice app, the app of Grit’s invoice tutorial, in about fifteen minutes: customers, products, invoices made of lines, a status and terms with labels, a switch, a due date added afterwards with nevela field, numbers nobody shares, and an invoice ready to print. A table says what each of Grit’s commands is here. CI builds it in a new app, as it does the others, and it is a post in each new app’s blog.
  • nevela field, to add a field to a resource that already exists, as Grit’s grit g field does. nevela field Invoice dueDate:date adds it to the descriptor, generates the resource again, writes the migration and runs it. It takes every field type, relations and defaults included, and several at once. Records already in the table keep what they have: a required field’s column is empty for them, and the form asks for it the next time each is edited. A field that is wrong changes nothing. Before, this took an edit to the JSON, nevela generate, a migration written by hand and nevela migrate, and the Contacts tutorial now does it in one line. See nevela field. In an app already made, run nevela update for the nevela command to know it.
  • A Print button on every record’s page, as Grit’s detail pages have, so an invoice or an order can go on paper or into a PDF with nothing to set up. It prints the app’s name, the record’s fields and its lines with their total, in black on white whichever theme is on, without the sidebar, the header or the buttons, and a long table runs on from page to page with its headings on each. An app that changed components/dashboard/record-detail.tsx keeps its version on upgrading, without the button; the new version is left in apps/web/.nevela/incoming/ to compare. See Printing a record.

Fixed

  • Records made at the same moment each get their own number. A numbered field (number:auto(INV)) took one more than the highest in the table, so two records made together could be given the same one, and the second was refused with an error. With six processes making 150 orders at once, 57 were refused; now none are. The last number given is kept in a new table, nevela_numbers, whose row is locked while the next is worked out. A number removed for good isn’t given again either. Run nevela migrate after upgrading; until then it works as it did. See Numbered by Laravel.

0.27.0 - 2026-10-30

What to install first, and the tutorials in every new app’s blog

Added

  • The tutorials in every new app’s blog, as Grit’s new apps have posts about Grit. The blog starts with a post for each of Nevela’s tutorials, its cover, what it builds, how long it takes and a link to it, and a welcome post that says how the blog works, in place of the three about the blog. The home page shows the newest three under “From the blog”, with a link to the rest. They are made in development only, as the sample posts were, and are the tutorials there were when that version of Nevela came out. An app made before this that has a blog gets the home page’s section with nevela upgrade, where its home page is the template’s; the posts are only for new apps. See The posts it starts with.
  • Set up your computer, a page before the Quickstart: what Nevela needs, how to check whether you have it, and what to install, in order, on macOS (Laravel Herd), Windows (Herd and Node.js) and Linux (php.new and Node.js), with what goes wrong most often and what to do. The Quickstart and every tutorial link to it, and nevela new points to its section for your system when PHP, Composer or Node.js is missing or too old, in place of php.net.

Changed

  • The blog has a heading of its own in the dashboard’s sidebar. A new app’s Posts is under Blog, and the resources you make with nevela resource are under Resources, which now always comes first, whatever the names in it. The Overview’s cards and its list put yours first the same way. Before, Posts was sorted in among yours, read as if you had made it, and could take a card from one of them. In an app created before this, add "group": "Blog" to apps/api/nevela/resources/post.json and run nevela generate.
  • A blog post’s picture in the list is 16:9, as the list shows it. The cover profile’s thumb was 600×300, and the cards cut a strip off each side of it; it is 640×360 now. Pictures uploaded before keep theirs.

0.26.0 - 2026-10-30

A billing tutorial, galleries, conditional fields, local phone numbers

Added

  • A fourth tutorial, A billing app: the client billing system JB builds on stage at GopherCon Africa, in Nevela’s commands. Clients with a Ugandan phone number, projects with a billing cycle only a recurring one has and a gallery, numbered invoices and payments, in shillings, then 500 clients, 2,000 projects, 25,000 invoices and 20,000 payments to see it hold up. A table puts JB’s Grit commands beside Nevela’s. Its steps are in examples/billing-app/, which CI runs in a new app like the others.
  • Several files in one field: gallery:files(image), in Grit’s words (gallery:images says the same). It holds up to 20, in the order they were added, each optimised on upload as an image field’s is. The dashboard’s form shows them as tiles to take out one by one, with a tile to add more, chosen or dropped several at a time; the table shows the first and how many more, and the record’s page all of them. The API sends the list of keys and, as galleryFiles, the details of each; each key has to have been uploaded to that field, once. The seeder gives one to four placeholder pictures. Not yet private, public, sortable or in a CSV. See Several files in one field.
  • Phone numbers of one country: phone:tel(UG) takes Ugandan numbers only. Written any way people write one there (0772 123456, 772123456, +256 772 123 456), it is kept the one way, +256772123456, and anything else is refused with “Enter a Ugandan number, such as 0772 123456 or +256 772 123456.” Laravel checks it in the form, the API, “Add several”, a CSV import, a public form and an action; the dashboard keeps the code at +256; the seeder makes Ugandan numbers. Kenya, Tanzania and Rwanda are known too. tel alone takes any country’s number, as before. In the descriptor, "country": "UG". See Phone numbers.
  • A field that only sometimes applies: cycle:enum(monthly|annually) if kind == recurring, in Grit’s words. The form shows it only for a recurring project and marks it required there; Laravel refuses a recurring project without one (“Needed when the kind is Recurring.”) and empties it on a one-off, whether a change sends it or not, however the record arrives; the seeder gives a cycle only to recurring projects. It depends on an enum or a yes/no field, for one value or several (if kind == recurring|retainer). In the descriptor, "when": {"kind": "recurring"}. See A field that only sometimes applies.

Changed

  • Contacts: your first app has a cover of its own, as the online shop and the student app do: the contacts app on a laptop, with a contact marked as a customer.
  • Seeded records read more like a business’s. Money in a currency without cents (UGX, RWF, JPY…) comes in thousands, UGX 1,250,000 rather than UGX 349; a client with a company of its own is a person at that company, not a second company; a project is called what work is called, “Stock system” or “School website”; and an address is a plot on a street in a city, not a sentence.
  • Projects built in Nevela shows a picture of each project, a screenshot of its site, where the first letter of its name stood. A project’s entry takes it as image. Kian Rover is there as it is now: an IT and software company in Kampala, live on Nevela, with its project briefs, internship applications, courses and blog.

0.25.0 - 2026-10-29

A student app tutorial, records each person sees, and unique pairs

Added

  • A third tutorial, A student app: teachers, courses, students and the enrolments that join them, each pair once; a role for teachers and a rule that keeps each to their own classes; a sign-up page whose students count once their address is proved; and a teacher told in the bell when a student drops a course. Its steps are in examples/student-app/, which CI runs in a new app like the others.
  • Which records each person sees: a visibleTo scope in a model says which of its records someone signed in may see. A teacher sees their own courses. Nevela asks it for the list and everything counted from it (the cards, the charts, the export, a relation’s picker), for one record (its page, changing and deleting it, its actions and private files, answered 404 when it is kept from them), for the records a relation may point at, for the trash, and for the bell, which tells each person of the records they may see and counts those. See Which records each person sees.
  • Fields unique together: --unique=student,course makes one enrolment for each student and course, a resource that links two others: a many-to-many. The table has the index, a create or change that would make a second is refused with a message on the field, the trash’s records count, many sent at once are kept apart from each other, and the seeder gives each record its own pair. In the descriptor, "unique": [["studentId", "courseId"]]. Added to an existing resource, nevela generate writes the migration for the index. See Many-to-many.

Fixed

  • Seeded records of a list that proves addresses are confirmed. Seeded after its form had "confirm", they were saved unconfirmed, so they weren’t counted, exported or told of, where the docs say a seeded record is confirmed as it is made.
  • A seeded school reads like one. A course is called Biology 101, with the code BIO-101, not Golden Keyboard; a teacher’s subject is Mathematics; a date of birth is between 16 and 60 years ago, not last month.
  • A public form can leave out a field Laravel fills. A sign-up form for students numbered number:auto(STU) was refused, because the number is required and the form doesn’t send it. A numbered field, and one copied from a related record, now count as filled.

0.24.0 - 2026-10-28

A shop tutorial, numbered orders, and prices from the product

Added

  • A second tutorial, An online shop with orders: categories, products with pictures and prices in a currency, orders whose items are edited inside them with a total the app keeps, a public part of the API, and a page of what is on sale. Its steps are in examples/online-shop/, which CI runs in a new app like the first. Its orders are numbered and its items priced from their products.
  • A field Laravel numbers: number:auto(INV), or Grit’s number:string:auto:INV, gives each new record the next number, INV-0001, INV-0002 and on, however it is made. Left empty in the form, it is filled when saved; one typed in is kept. In the descriptor, "auto": "INV". See Numbered by Laravel.
  • A field copied from a related record: price:money(product.price) takes an order item’s price from its product when the item is added, or changed to another product, and keeps it after, so an old order keeps its prices. It isn’t typed: an order’s items show it as soon as the product is picked, and what is sent for it is left out. In the descriptor, "from": "productId.price". See Copied from a related record.

Fixed

  • A seeded slug made from a field reads as that field does. A product called Quiet Backpack gets quiet-backpack-20, not a slug made of other words. Before, only categories’ slugs followed their names.

0.23.0 - 2026-10-28

A first tutorial, and tables that keep their shape

Added

  • Tutorials, a page of its own beside Projects built in Nevela: a card for each tutorial with a picture of what it builds, its level and time, and what it covers. The first is Contacts: your first app: companies and the people at them, built from an empty folder in eight steps, from nevela new to a field added later, an action, roles and the API. Every step is in examples/contacts/, which CI runs on a new app on every change, so the tutorial can’t drift from what Nevela does.
  • More icon names a resource can have, by Lucide’s own spelling: building-2, contact, tags, shopping-cart, graduation-cap, book-open, school and newspaper. The docs now say which ones the dashboard knows, and that an app can add others.
  • A table shows its first six columns, and keeps each to a set width. A value too long for its cell ends in ”…” and shows whole when you point at it. Long text and files that aren’t pictures start off, the rest of the columns are in the Columns menu, and a field’s "list" in the descriptor decides for it: true always on, "hidden" off until turned on, false none. Long text, a description or notes, can now be turned on as a column; before, it never could. See Which columns the table shows. Run nevela generate after updating for it to apply to your resources.

Fixed

  • A wide table no longer makes the whole dashboard wider than the window. With many columns, the cards above the table, the toolbar and the header were pushed off the right of the screen. The table scrolls in its own box now.
  • A relation to a record you may not see says “Hidden”, in the table and on the record’s page, instead of showing its id and linking to a page that would turn you away.
  • Seeded data reads like real data. The first seed of an empty table numbers its rows from 1 (ada.okafor12@example.com, not ada.okafor1705000012@example.com), and a resource called Company, Supplier, Client, Agency or the like gets company names (Acme Ltd, Globex Group) instead of product names.

0.22.0 - 2026-10-27

Line items, and docs that say what is true now

Added

  • Line items: an order’s items, an invoice’s lines, edited as a table inside its form and saved with it. nevela resource Order --fields="…" --items="OrderItem: product:belongsTo(Product), quantity:int, price:money" makes both resources, and gives the lines a field pointing at their order (Grit’s --items spelling works too). In the order’s form, below its fields, the lines are a table: a row for each, a product picked as anywhere else, rows added and removed, and each checked with OrderItem’s own rules before anything is sent. When the lines have a quantity and a price, each line’s amount and the total are shown as you type, and again on the order’s page. The order and its lines are saved together or not at all; deleting the order puts its lines in the trash with it, and restoring it brings them back. Order items stay out of the sidebar and the Trash page, and their changes don’t ring the bell for the order’s. Whoever may edit an order may change its lines. In the API the lines travel with one order as items: a line with its id is changed, one without is added, one left out is removed, and a mistake is named by its place (items.1.quantity). To store a total, give the model an itemsSaved() method; Nevela calls it once the lines are saved. A resource you already have gets lines with "items": "OrderItem" in its descriptor. See Line items.

Changed

  • The docs say what is true now. Releases had updated only the pages a change touched, so the overview pages had fallen behind. The home page’s questions said Nevela was not production-ready because relations, uploads and account pages were “still to come”; they now say what being 0.x means, what isn’t there yet, and how to use Nevela with an app you already have. Its features show what has been added since: roles, Google and GitHub, relations, files, the trash, notifications and the activity log, and the public site. How Nevela is built says how each change is tested and has a current roadmap. The reference pages gained what they were missing: the scheduled tasks, the social sign-in endpoints, the roles and permissions on /auth/me, the currency and auth.social settings, three web app variables, and the belongsTo and file keys of a descriptor’s field. Releasing now has a step that checks the docs before each release.

Fixed

  • Resources made together get their migrations a second apart, in order, so the table of an order’s lines is created after the orders table it points at.
  • A new record’s page says “Add an order”, not “Add a order”.

0.21.0 - 2026-10-27

An activity log, and the bell tells others when records change

Added

  • An activity log: who created, changed, deleted, restored or removed which records. Every write to a resource’s records by someone signed in is noted, whether it came from the dashboard, an import, an action or the app’s own code, from Eloquent’s own events. The same thing done to many records by one person within two minutes is one line (“You deleted 20 products”), so a selection deleted or a file imported one row at a time reads as one. Recent activity on the dashboard’s home page shows the latest eight, and Activity under Manage has all of it, by resource and by what was done. It is for roles that include the new Activity permission (activity.view, under Access); administrators have it, and each person sees only the resources they may view. GET /_nevela/activity serves it. Rows are kept for 180 days. Seeding, the scheduler and visitors leave none. Run php nevela migrate for its table. Modelled on Grit’s activity log, without its hash chain.
  • The bell tells everyone else when records are created, deleted or restored. On a team, someone deleting a product now reaches the others who may see products: “Ada deleted a product: Lamp”, or “Ada deleted 20 products” for a batch, one line per person and kind while unread, with the count. Changes to a record go only to the activity log, so fixed typos don’t fill the bell. What you did yourself isn’t in your own bell; it is in the activity log. Notice takes a count, for one notice that stands for several things.

0.20.0 - 2026-10-26

The dashboard’s bell works, and the sign-in password has an eye

Added

  • The bell in the dashboard’s header tells people what happened behind the scenes. It was there with nothing behind it. Now a visitor sending a public form tells everyone who may view that resource, and so does someone confirming their address on a form that asks for it. A new account, by sign-up or a social sign-in, tells whoever may view users; a closed one tells whoever may restore it. Changes to how you sign in (password changed or reset, two-step sign-in on or off, a passkey added or removed) and an administrator changing your roles or password are told to you. A queued job that fails for good, and the night’s clear-out of the trash, are told to the administrators. Several of a kind that arrive before they are read are one line with a count (“14 new enquiries”); a warning colours the bell; opening one marks it read, and Mark all read does the rest. The dashboard asks again every minute while it is in view. Above them, an administrator sees what is wrong with the app right now: migrations not run, a newer Nevela, jobs waiting with no worker, and in production a scheduler that isn’t running, mail going to the log or a cache that keeps nothing. Your own code tells people with Notices::toPermission('orders.view', new Notice(…)), Notices::send() and Notices::toAdmins(). Run php nevela migrate for its table. See Notifications.

  • The sign-in password has an eye that shows what you’ve typed. Sign-up, reset and the change-password page had one; the box people use most didn’t. Clicking it again hides the password, and signing in works either way. The “Your password” box that closing an account and turning on two-step sign-in ask for has it too. All of them now share one PasswordInput in components/auth/password-field.tsx, which takes a ref, so the sign-in step still puts the cursor in it.

0.19.2 - 2026-10-26

nevela upgrade no longer stops at the old range’s newest patch

Fixed

  • nevela upgrade goes all the way to the newest release when the app’s range still had a newer patch. An app on 0.5.1 with "nevela/laravel": "^0.5" was moved to 0.5.3, the newest 0.5 release, and the upgrade ended there without a word while 0.19.1 was out. The range was only widened when Composer changed nothing at all. Now it is widened whenever Composer stops short of the newest release, and the “looks deliberate” note for a pin or a hand-written range shows up in that case too. When Composer has moved the package only part of the way, the dashboard is still brought up to the version that was installed. (#76)

0.19.1 - 2026-10-23

A new app’s install gets past a download Windows refuses

Fixed

  • nevela new tries Composer again when a download doesn’t go through. On Windows the first files Composer writes into a new app’s vendor folder can be refused (“could not be written … Permission denied”), most likely while antivirus looks at them, and the install stopped there. It failed three new apps in four on one machine, always on the first download. A second run goes through, so the installer now runs composer install up to three times when a download couldn’t be written or fetched. What already arrived is in Composer’s cache. A problem that lasts, such as a version that can’t be had or a missing PHP extension, still stops it at once. If downloads keep failing, it says to run it again and how to keep antivirus out of the folder.

0.19.0 - 2026-10-22

SEO for every app: robots.txt, share images, icons and noindex

Added

  • What search engines and shared links are told, in every new app. It all comes from lib/site.ts through lib/seo.ts, with NEXT_PUBLIC_SITE_URL as the site’s address.
    • A share image (app/opengraph-image.tsx, also used for X): the site’s name and tagline on the theme’s brand colour. A link pasted into WhatsApp, X or LinkedIn shows a card, not a bare address.
    • An icon for the browser tab and a phone’s home screen (app/icon.tsx, app/apple-icon.tsx): the site’s first letter on its brand colour. Browsers used to get a 404 for /favicon.ico.
    • robots.txt: the site readable, /dashboard and /api not (stored files, which previews fetch, excepted), and the sitemap named when there is a blog.
    • noindex on the dashboard and every page of signing in, so a sign-in screen isn’t listed in search results.
    • metadataBase, so canonical links and the share image are absolute, and Open Graph and X cards on every page.
    • Structured data (schema.org): WebSite and Organization on the home page, and BlogPosting for each post of a blog made with nevela blog from now on.
  • The web app guide says what each file does, and how to swap in a designed image or icon.

0.18.0 - 2026-10-22

nevela resource:remove, and a guide to deploying on Laravel Cloud

Added

  • nevela resource:remove Product takes a resource out of the Laravel app and the dashboard. Kian Rover removed four by hand, each about twenty files across both apps. Closes #59.
    • It shows first. Without --force it lists what it would do, and nothing changes.
    • What is still as Nevela wrote it is deleted: the descriptor, model, request, API resource, controller, policy, .resource.ts, pages and actions. Then the routes, the dashboard’s menu and the related resources are regenerated, and its permissions come out of every role.
    • What you have changed is listed and kept, unless --with-yours. An adopted model loses only Nevela’s block.
    • The table and its rows stay. --drop-table writes a migration that drops it, for you to run.
    • It refuses while another resource belongs to it.
    • It lists your own code that still uses the resource: code that would no longer build, and what reads or posts to its public section, which builds and then fails in use, a page when it loads and a form when it is sent. For the blog’s Post, that is the /blog pages, through lib/blog.ts. Code in comments doesn’t count.
  • Deploying to Laravel Cloud, a guide in the docs to both applications, step by step.
    • The two root directories, and every variable with which ones must match.
    • Neon’s pooled address for the app, and its direct one for migrations.
    • The pnpm build command, the scheduler and a queue worker, and making the first administrator.
    • Checking it all with nevela deploy:check, and changing to your domain.
    • Running one web replica until the web app has a shared cache, and a table of symptoms and their causes.
    • Closes #63.

0.17.0 - 2026-10-22

nevela deploy:check: what a server needs, checked after each deploy

Added

  • nevela deploy:check (php artisan nevela:deploy:check on the server) checks what a deployed app needs and a local one doesn’t, and names what to change for each problem. Part of #63.
    • This app: APP_KEY, APP_DEBUG off, migrations (with a hint about pooled database addresses), a cache that keeps things between requests, the scheduler, a queue worker and mail.
    • Signing in: NEVELA_WEB_URL, NEVELA_PROXY_SECRET and an administrator who can sign in.
    • The dashboard, asked with the shared secret: whether it reaches the API, whether the two secrets are the same, and whether NEXT_PUBLIC_SITE_URL matches.
    • It exits with an error when something is wrong, so a deploy script can stop on it.
  • The scheduler leaves a sign every 5 minutes, which is how deploy:check knows it is running, and the queue check sends a job that does nothing but say it ran.
  • The dashboard answers GET /api/nevela/health with what it sees, only to a caller with the shared secret.
  • nevela status points to deploy:check in production.

0.16.0 - 2026-10-22

Reset a password, verify or promote an account from the command line

Added

  • nevela user <email> changes an account that exists. nevela user used to refuse an email in use (“Someone already has this email”), and “Forgot password” needs mail and a queue worker a new server may not have yet. What was left was tinker, with the new password in the shell’s history. Closes #62.
    • --reset gives it a new password, asked for twice and not shown, and checked as the dashboard checks one. It is never taken from the command line. Where nothing can ask, --password-stdin reads it from standard input.
    • --sign-out-everywhere ends every sign-in and token the account has.
    • --verify marks the address verified, and --role=ADMIN gives it a role as well as the ones it has.
    • --link prints a sign-in link that works once, within 15 minutes. It still asks for a second step, and doesn’t mark the address verified, since it wasn’t sent there.
    • Everything is checked before anything is changed, a closed account is refused, and nevela user <email> alone describes the account.
  • nevela status names the administrators who can sign in, and is red when there are none.

0.15.0 - 2026-10-21

The dashboard says when NEVELA_API_URL or the proxy secret is wrong

Added

  • The dashboard checks that it can talk to the Laravel app, once when it starts, and writes what is wrong to its log with what to change. In development the sign-in page shows it too.
    • The address: a NEVELA_API_URL without its /api, the usual slip with the bare address a host such as Laravel Cloud gives, is named with the address to use. So is an address where nothing answers as Nevela, or a Laravel app that can’t be reached.
    • The secret: a NEVELA_PROXY_SECRET that differs between the two apps, or is set in only one. It used to fail quietly: every device was listed with the dashboard server’s address.
    • Laravel’s auth/config answers proxySecret, which says whether the secret the dashboard sent is its own. Closes #61.

Changed

  • A sign-in that reaches the wrong address says so. Laravel’s “The route auth/token could not be found” becomes “The dashboard can’t find the API’s sign-in. Check NEVELA_API_URL”, with the address it asked at, in development.
  • .env.example in the web app says the prefix is part of NEVELA_API_URL (https://api.example.com/api, not the host alone), and lists NEVELA_PROXY_SECRET.

0.14.0 - 2026-10-21

A quote from Nevela’s maker, real customers, and Docs on the home page

Changed

  • A new app’s quote is Nevela’s maker’s, not a made-up one. The sign-in screen and the home page showed “We moved our whole workflow over in an afternoon”, from an “Alex Rivera” who doesn’t exist. They now say “One place to change it. That was the whole idea.”, from MarkCole MUKISA, Creator of Nevela Framework. Put yours in testimonial in lib/site.ts. Part of #60.
  • The logo strip lists apps built with Nevela: Kian Rover and IKIPS, each a link, and Rotus Imeir, in place of Acme, Globex and the rest. A customer in site.ts can have an href.
  • Docs in place of Contact on the home page’s menu and footer, linking to the Nevela docs. Contact went to support@example.com.
  • An upgraded app keeps its own site.ts, as before, and the pages read it in its older shape too: its customers as plain names, and a Docs link to the Nevela docs.

0.13.0 - 2026-10-21

nevela publish, and a sign-in page that says when Google has no keys

Added

  • nevela publish writes config/nevela.php for you to change, in place of php artisan vendor:publish --tag=nevela-config (which still works, as does nevela publish --tag=nevela-config). If the file is already there, it is left alone and the command names the settings it doesn’t have; --force starts it again from Nevela’s. The docs now say which settings need no file because they come from .env, such as SOCIAL_AUTH_ENABLED and NEVELA_REGISTRATION.
  • The sign-in page says when Google and GitHub sign-in has no keys. With SOCIAL_AUTH_ENABLED=true and no provider’s client ID and secret, there are no buttons, and nothing said why. In development the page now says which variables to set in apps/api/.env. Laravel’s auth/config answers socialNeedsKeys, which is never true in production. The docs’ Google and GitHub section is now steps, in order.

0.12.1 - 2026-10-21

Sign-ins end in apps whose config/nevela.php is from before 0.12

Fixed

  • A published config/nevela.php no longer hides the settings added since. Laravel merges a package’s config one level deep, so the auth section of a file from before 0.12 replaced Nevela’s whole: auth.session was missing, and sign-ins in an upgraded app had no idle or absolute limit at all. auth.social was missing too, so SOCIAL_AUTH_ENABLED=true did nothing in an app from before 0.10. Nevela now merges its config key by key: a setting your file doesn’t have takes Nevela’s value, and one it does have wins. A list (middleware, rich_text.tags) and an allowlist (rich_text.attributes) are yours whole, as is each image profile you define. Only a limit set to null or 0 means no limit. nevela upgrade and nevela status name the settings your file is missing, and the release that added each. Closes #58.

0.12.0 - 2026-10-19

Faster and ready for Octane, with sign-ins that end, as in Grit

Added

  • A benchmark, in benchmarks/, modelled on Grit’s: plain Laravel, plain Laravel behind Sanctum, and the API Nevela generates, answering the same requests with the same JSON in production PHP-FPM, one at a time, against one Postgres. It runs with Docker (./run.sh) and on GitHub as the Benchmark workflow. The first results, on the docs’ new Benchmarks page: Nevela serves four requests for every five that Laravel with Sanctum does, and the page says where the rest goes.
  • Sign-ins that end, as in Grit. A sign-in is now a 15-minute access token and a refresh token that is swapped for a new one each time it is used. A sign-in ends after 7 days unused or 30 days however busy (NEVELA_SESSION_ACCESS, NEVELA_SESSION_IDLE, NEVELA_SESSION_ABSOLUTE, in minutes). A refresh token used a second time, however many swaps ago, ends that sign-in on every device holding it; only a second request that set out with the same token at the same moment, within a minute (reuse_seconds), carries on. When the access token is about to run out, proxy.ts swaps the refresh token on the next page or API call, so nobody working is interrupted, and an ended sign-in lands on /sign-in saying why. After 14 min 30 s with no activity it asks “Still there?”, counts down 30 s and signs out (NEXT_PUBLIC_SESSION_IDLE_MS, NEXT_PUBLIC_SESSION_COUNTDOWN_MS); activity in another tab counts. Account → Devices shows when each sign-in ends, nevela status shows the limits, and the scheduler removes ended sign-ins nightly. Run php artisan migrate. Closes #55.

Changed

  • Faster requests. Nevela checks that a migration’s table or column is there before using it, so an app that hasn’t migrated yet keeps working. The answer was remembered for one request only, and PHP-FPM starts every request afresh, so a deployed app asked the database about the roles table and the trash column on every request. A yes is now kept across requests in bootstrap/cache/nevela-schema.json, and forgotten when migrations run or by php artisan optimize:clear. Against Laravel with Sanctum, Nevela went from 0.79–0.83× to 0.83–0.88× the requests a second in the benchmark, and a single read uses half the database CPU it did.
  • Ready for Octane and queue workers. A process that serves many requests (Octane) or jobs (queue:work) now starts each one without what Nevela kept for the last: whose roles grant what, the uploads a page looked up, and the note of which tables and columns are there, which is read again, so a migration run from another process is seen. The benchmark measures Nevela on Octane with FrankenPHP too: 1.4 to 1.8 times as many requests a second as on PHP-FPM. See Faster, with Octane.
  • Tokens that belong to no sign-in now end too: those from before this version, and any your code makes with createToken(), keep to the same idle and absolute limits, measured from their last use and creation. A dashboard signed in before the upgrade stays signed in until its token reaches them.
  • POST /api/auth/token and the other sign-ins answer with more: expiresAt, refreshToken and refreshExpiresAt beside token. An API client should refresh before expiresAt (POST /api/auth/refresh); one that doesn’t is signed out after 15 minutes. Breaking for API clients that keep one token for good.

0.11.0 - 2026-10-18

Enum values in words, and money in its own currency

Added

  • What an enum’s values are called. "optionLabels": { "asap": "As soon as possible" } on an enum field, or timeline:enum(asap=As soon as possible|month=Within a month) in --fields. The value stays what is stored and sent; the dashboard shows the words in the table, filters, form, record page, stat cards, charts and action sheets. A value with no label reads as before. $record->optionLabel('timeline') on a generated model, and optionLabel() on the descriptor’s field, give an app’s emails and PDFs the same words. A label for a value the field doesn’t have is refused.
  • A currency for money. NEVELA_CURRENCY=UGX for the app, or "currency": "UGX" on a money field. Money is written in it with its own decimals (UGX 4,500,000, $4,500,000.00) in tables and on a record’s page, the input shows the code in place of $, and a currency with no decimals takes whole numbers. Action sheets do the same. A code that isn’t ISO 4217’s is refused. With neither, money looks as it did. Closes #49.

0.10.0 - 2026-10-18

Sign in with Google or GitHub, behind one switch

Added

  • Signing in with Google and GitHub, on Laravel Socialite. SOCIAL_AUTH_ENABLED=true in apps/api/.env switches it on for the whole app, and a provider shows once its two keys are set: GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET, as Grit names them. The dashboard asks Laravel which providers to show on each page, so the switch needs no generate and no rebuild. Who gets in follows registration: off, only someone with an account, matched by the provider account connected to it or by an address the provider says is verified; on, a new address gets a new account. Two-factor still applies afterwards, and closed accounts and blocked addresses are refused. An account whose address was never verified here is taken over by the person the provider vouches for: its password stops working and its devices are signed out, since anyone could have registered it in their name. Account → Security → Connected accounts connects and disconnects them. The browser never talks to Laravel and never holds a token: the dashboard’s server starts the sign-in and hands back the code, and the state is good once, in the browser that asked. nevela status says which providers are on. See Google and GitHub.

Changed

  • The package requires laravel/socialite (^5.31).
  • Which social providers the dashboard shows comes from enabledSocialProviders() in lib/social.ts, which asks Laravel. The one in the generated lib/auth-config.ts is kept so older pages still build, and shows none.

0.9.2 - 2026-10-13

A public form’s files, uploaded by the form hook

Added

  • usePublicForm uploads files. A file input in the form is sent in the two steps Laravel wants: the file first, then its key as the field’s value. What Laravel refuses is shown under the field; a file already uploaded isn’t uploaded again when the form fails for another reason. form.uploading names the field in flight, form.upload(field, file) does one by hand, and values gets the keys as its second argument.
  • A form’s file can be sent to the form’s own address, PUT /api/public/<slug>/_uploads/<field>, so a page needs only the slug. The address by the resource’s name still works.

0.9.1 - 2026-10-12

A robot check counts only if it was solved on your site, for that form

Changed

  • The robot check is tied to the site and to the form. Cloudflare’s yes is now taken only if the check was solved on the web app’s own address (NEVELA_WEB_URL), or one of TURNSTILE_HOSTNAMES, and under the form’s own name, which <PublicFormGuard> now renders the widget with. A widget usually lists localhost beside the real domain; before this, a token solved on someone’s own machine was good on the live form. In production localhost is never accepted and Cloudflare’s test keys are refused. A live site whose NEVELA_WEB_URL is still localhost answers 503 and nevela status says why. GET /api/public/_nevela/form/<slug> returns the action for a form you render yourself. See Where a check counts.
  • A robot token is taken once by this app, whatever Cloudflare says to it again. Trying a real widget in a browser, the same token sent three times was answered yes by Cloudflare three times, where its documentation says a second use is refused. Laravel now remembers each token it has taken for ten minutes, in the cache, and refuses it a second time without asking.

Fixed

  • PublicMail::toVisitor() and toOwner() called while a record is being saved (a model’s created) now count and send once the save has committed, not inside its transaction. A record that is rolled back sends nothing. On Postgres with the database cache, a lock held by another request could abort the transaction and lose the record. Inside a transaction they answer true: whether the email went is decided at the commit.
  • On Postgres, an address with something that couldn’t be an id in it (/api/_nevela/users/nobody) answered 500 where it meant 404: Postgres refuses to compare a number or UUID column with it. An id’s shape is now checked first, for users, deleted accounts, blocked emails, roles, passkeys, sessions, and a record’s trash, actions and private files.
  • Removing a record from the trash for good while others still belong to it no longer aborts a surrounding transaction on Postgres.

0.9.0 - 2026-10-12

A blog with every new app, and public forms that keep bots out

Added

  • A blog. A new app has one: a Post resource to write in under Posts in the dashboard, /blog and /blog/<slug> on the site, an RSS feed at /blog/feed.xml, a sitemap, a Blog link in the site’s header, and three sample posts. The pages are written once into apps/web and are yours. nevela new my-app --no-blog leaves it out, and nevela blog adds it to an app that has none. For posts in a table of the app’s own, nevela blog --resource=Post --title=… --body=… writes only the pages. See The blog.
  • A slug that fills itself. slug:slug(title)!, or "from": "title" in the descriptor: left empty on create, the slug is made from that field, and -2, -3 are added while it is taken, counting records in the trash. In the dashboard’s form it follows the title as it is typed. It is never remade when the title changes later.
  • Publishing. "publish": "publishedAt" in a descriptor names the date a record is published by. The dashboard shows a Published, Draft or Scheduled badge in place of the date, a filter on it, and Publish and Unpublish on the record’s page and in its row’s menu, under the permission to edit. filter[publishedAt]=draft (or published, scheduled) narrows a list over the API. A model generated for such a resource has a publicQuery scope that lets through the records whose time has come.
  • Protection for a public form. "protect": { "turnstile": true, "honeypot": true, "minSeconds": 3, "email": "email" } on a public.create. Laravel checks, cheapest first and before anything is validated or stored: a field no person sees, the time the form took (by a signed token it hands out at GET /api/public/_nevela/form/<slug>), Cloudflare Turnstile, whether the address’s domain takes mail or is a throwaway one, and how often that address has sent the form from anywhere. A bot is answered 201 and nothing is stored; a person who fails the robot check is told so; a bad address is a message on its field. Turnstile is verified by Laravel with TURNSTILE_SECRET_KEY. With no secret the check is skipped in development, and in production the form answers 503 and nevela status is red: it never falls open. A form with no protect is unchanged. See Protecting a public form.
  • What a form blocked. Every refusal is counted by resource, reason and day, and the resource’s page in the dashboard shows the week: “Blocked this week: 132 (118 robot check, 14 throwaway address)”. Also at GET /api/_nevela/forms/<slug>.
  • Limits on the mail a form causes. PublicMail::toVisitor($address, $mail) writes to an address at most once an hour and three times a day, across every form, and drops the rest, so a form can’t be used to mail strangers. PublicMail::toOwner($mail, line:, url:) sends ten notices an hour as they happen and holds the rest for one email at the top of the hour: “14 more enquiries since 14:05”. Both are queued, and the limits are in config/nevela.php under public.
  • Proving an address. "confirm": "email" on a public.create, for a list people join. The record is saved unconfirmed and a link is emailed; until it is followed the record is marked Not confirmed in the dashboard and left out of counts, charts and the export, and after 48 hours it is removed. Signing up twice answers the same as the first time, so the form doesn’t say who is on the list. Subscriber::confirmed() is who to write to. The link opens /confirm in the web app.
  • usePublicForm() and <PublicFormGuard> in the web app: a public form in a few lines, with its token, the honeypot, the Turnstile widget (loaded once, reset after every attempt, set with NEXT_PUBLIC_TURNSTILE_SITE_KEY), and 422 issues sorted onto their fields.
  • nevela disposable fetches the current list of throwaway email domains, and nevela digest sends the held notices by hand.

Changed

  • A public create that has protect or confirm answers 201 with no body, even where the resource has read: the answer to a form that was taken has to be the answer to one that was quietly turned away.
  • nevela dev works the queue as well, where the app’s queue isn’t sync, so queued mail is sent while you develop.
  • nevela new creates the blog unless told --no-blog, so a new app starts with one resource and three records in it.

0.8.0 - 2026-10-11

Adopt the tables you have, and open part of them to the public

Added

  • nevela adopt <table>: make a resource of a table you already have. The descriptor is read from the table: nullable columns are optional, a unique index is !, and a foreign key to a table that is already a resource is a belongsTo. It shows what it read and what it left alone, and asks before writing. The table is not changed and no migration is written to create it; nevela migrate afterwards adds the deleted_at column that gives it a trash. A column with no field kind, such as json, stays in the table untouched by the API. See Adding Nevela to an app you already have.
  • Integer ids. A resource can have the numbered ids of $table->id() in place of UUIDs: nevela resource Note --fields="…" --id=int, or "id": "int" in the descriptor, which is what adopting a table with integer ids writes. A relation’s column follows the resource it points at, so a resource with integer ids and one with UUIDs can belong to each other. An id is a string in the API either way. nevela seed fills both. Nothing is generated differently for a resource with UUID ids: after upgrading, nevela generate reports every resource file unchanged.
  • Rich text. body:richtext is a field with an editor in the dashboard: bold, italic, strikethrough, links, headings, lists, quotes, undo and redo. It is stored as HTML, and Laravel cleans that HTML against a list of tags (rich_text in config/nevela.php) when a record is saved and again when it is read, so <p onclick="x()">Hi<script>alert(1)</script></p> is stored as <p>Hi</p> whether it came from the form, the API, “Add several” or a CSV import. A record’s page shows it formatted, a table shows its first words, and nevela seed writes a few paragraphs with a heading and a list. See Field types.
  • Actions on a record. An actions section in a descriptor names what can be done beyond create, edit and delete: accept an application, send an announcement. nevela generate writes a class for each, once (app/Nevela/Actions/<Resource>/<Action>.php), and you write what it does in handle(). Nevela gives it the route, a button on the record’s page and in its row menu (or beside New, for one on the list as a whole), a confirmation, a sheet for what it asks for, the message it returns as a toast, and a database transaction around it. Each is a permission of its own on the Roles screen (internship_applications.accept), which an administrator has and nobody else does until given it by name. See Actions on a record.
  • Private files. A file field can be marked private (cv:file(pdf|private), or "private": true in the descriptor). The file is kept on uploads.private_disk, which the web server doesn’t serve, and its key opens nothing: GET /_nevela/files/<key> answers 404. It is fetched from GET /_nevela/private/<slug>/<id>/<field> by someone signed in who may view that record, with Cache-Control: private, no-store. The dashboard shows a download in place of a public link. It stays unreachable while its record is in the trash, and is deleted when the record is removed for good. See Files and images.
  • A public site on your API. A public section in a descriptor opens part of a resource to anyone, with no sign-in: read (the fields that may be seen, and the unique field one record is fetched by) and create (the fields a visitor may send, and a throttle). The routes are under /api/public/<slug>, only for what a section names, and are listed in routes/nevela-public.php. Which records can be read is the model’s publicQuery scope, which lets nothing through until you write it. A field that isn’t listed can’t be reached by sorting, filtering or search either. A form can carry a file: PUT /api/public/_nevela/uploads/<Resource>/<field> gives a key that is good once and for an hour, and uploads never used are removed each night. Each resource’s reading, its form and its upload are throttled apart, for each visitor: through the web app a visitor is counted by the address the proxy in front of it saw, so set NEVELA_TRUSTED_PROXIES in the web app if there isn’t exactly one. In the web app, laravelPublic() reads what is public into Next’s cache, which the dashboard revalidates when it saves a record. See A public site on your API.
  • A field can have a default: status:enum(pending|paid)=pending, or "default": "pending" in the descriptor. It is what the field is when a create leaves it out, and the column’s default. An adopted column brings its own.
  • A string or text field can have a length of its own: excerpt:string(500), or "maxLength": 500 in the descriptor. The column, the validation and the dashboard’s form use it. An adopted varchar(500) keeps its 500.
  • The docs’ changelog page opens with Releases by week: every release as a version and one line saying what it was about, grouped by the week it came out, each linking to its full entry below. The entries follow as before.
  • Each release has that line in CHANGELOG.md, in italics under its version. pnpm release says so when the notes for a new one have none.

Changed

  • In a role’s grants, * after the dot (products.*, @resources.*) means create, view, edit and delete, as it always has in practice: those were the only four. A resource’s own action is not covered by it, only by its own name or by * alone. No role changes what it allows by upgrading.
  • resources/index.ts in the dashboard also exports extras, which nevela generate writes.
  • nevela generate writes routes/nevela-public.php in every app. With no public section anywhere it holds no routes.
  • nevela trash also removes files uploaded through a public form and never used.

Fixed

  • A record could be made to belong to one in the trash. A product could be created in, or moved to, a deleted category, which no list shows and whose page is a 404. It is refused now, in the form, the API and “Add several”, with “This one is in the trash. Restore it, or choose another.” Records that already point at a deleted one are left as they are.
  • Filtering a list by a relation with something that can’t be an id (filter[categoryId]=nonsense) answers with no records. On PostgreSQL it was an error.

0.7.1 - 2026-10-09

An email nobody had verified said “Verified”

Fixed

  • An email nobody had verified was shown as “Verified”. Accounts made with nevela user, added on the Users screen, the starter admin@example.com and the sample users were all marked verified when they were created, though no link or code had ever been sent to the address. They now start as “Not verified”, which is what they are, and become verified when their owner proves the address. nevela user --verified marks one by hand, for an address you know is right. Accounts made before this keep the mark they have. If your app sets require_email_verification, an account an administrator adds is now sent a verification link the first time it signs in.

0.7.0 - 2026-10-09

Deleted accounts, kept and restorable

Added

  • Deleted accounts. A page under Manage that lists the accounts that were closed, with their roles, when they were closed and by whom. Restore opens one again exactly as it was; Remove for good erases it. For anyone who may delete users, under the Users screen’s rule: only accounts that may do no more than you.
  • Close account, at the foot of Account → Profile: someone closes their own account with their password. It is signed out everywhere and kept for an administrator to restore. The only administrator can’t. auth.close_account in config/nevela.php switches it off.
  • An email that had an account can’t sign up again, while its account is closed and after it is removed for good. Other spellings of the same mailbox count as the same: capitals, a +tag, and at Gmail the dots. After removal only a fingerprint of the address is kept (an HMAC keyed with the app key) and a hint such as m•••@gmail.com; Allow again on the Deleted accounts page frees it.
  • POST /auth/close, GET /_nevela/deleted-accounts, POST /_nevela/deleted-accounts/{id}/restore, DELETE /_nevela/deleted-accounts/{id}, GET /_nevela/blocked-emails and DELETE /_nevela/blocked-emails/{id}.

Changed

  • Deleting a user closes the account (DELETE /_nevela/users/{id}, and Delete on the Users screen), where it removed the account with its roles and sign-in methods. A closed account can’t sign in, is sent no sign-in links or password resets, isn’t listed among the users and isn’t counted as holding its roles. In an existing app this starts when nevela migrate has run the migration that comes with the upgrade; until then deleting removes, as before. Code of your own that lists or counts users sees closed accounts too: start from ClosedAccounts::open(). See Deleted accounts.
  • nevela status counts the users who can sign in without the deleted accounts, and a resource’s records without what is in the trash, and says how many of each are being kept.

0.6.0 - 2026-10-09

The trash: deleted records, restorable for 30 days

Added

  • The trash. A deleted record is kept for 30 days and can be restored. A Trash page under Manage lists what has been deleted, a tab per resource, with Restore, Delete forever and Empty. Every delete in the dashboard says where the record is going, and the message that confirms it has an Undo, for one row or a whole selection.
  • Deleted records are hidden from lists, counts, stats, insights, exports and their own pages. They are removed for good each night by the scheduler, whenever the Trash page is opened, and by the new nevela trash. trash.days in config/nevela.php sets how long they are kept; null keeps them until someone removes them.
  • Who may use it follows the permission to delete: a generated policy has restore and forceDelete, and a policy from before this is asked what it says to delete.
  • GET /_nevela/trash, GET /_nevela/trash/{slug}, POST /_nevela/trash/{slug}/{id}/restore, DELETE /_nevela/trash/{slug}/{id} and DELETE /_nevela/trash/{slug}?confirm={slug}.

Changed

  • Deleting a record moves it to the trash, in the dashboard and over the API (DELETE /{slug}/{id}), where it removed the row. Generated models use Nevela\Laravel\Concerns\Trashable, which is Laravel’s soft delete. In an existing app this starts when nevela migrate has run the migration nevela upgrade writes for each resource (add_trash_to_…); until then delete works as it did. A query of your own that reads a resource’s table with DB::table(…) sees deleted rows, and a unique value is held until its record is removed for good. See The trash.
  • nevela upgrade says so when it finishes on a version older than the newest release, which happens in the few minutes a release takes to reach Composer, and what to run.

0.5.3 - 2026-10-08

Insights above every resource’s table

Added

  • Insights, above every resource’s table: a panel with a bar chart of records created per day, week or month, and how the records split across each enum and yes/no field. It follows the table’s search and filters, so narrowing the list redraws the charts for what is left. Closed until opened, and nothing is counted until then.
  • GET /{slug}/_insights behind it. Existing apps get it when nevela upgrade regenerates their controllers and routes.

0.5.2 - 2026-10-08

Add several records at once

Added

  • Add several, beside New and Import on every resource’s list: a grid for typing in several records at once. It opens with five blank rows, ignores the ones left empty, and the button says how many it will create. They are saved together or not at all, and a mistake is shown on its row.
  • POST /{slug}/_bulk behind it: up to 500 rows a request (bulk_max), checked with the rules for creating one and written in a single transaction. Existing apps get the endpoint when nevela upgrade regenerates their controllers and routes.

Changed

  • nevela upgrade opens with the name drawn large, as nevela new and nevela update do, says which version the app is on, and ends with the version it is on now.

0.5.1 - 2026-10-07

The creator’s credit, and nevela --version

Added

  • The docs home page credits Nevela’s creator: why he built it, in his own words, and where to follow him.

Changed

  • A new app’s home page says “Built with Nevela (Next.js + Laravel)” in its footer, where it said “Built with Flare”. An existing app gets the line on its next nevela upgrade, if its home page hasn’t been changed.

  • nevela --version shows what nevela version shows: the command’s version and how it was installed, and the app’s version when you are in one. Piped or captured, it still prints the number alone, for scripts. The docs use nevela --version.

  • The docs lead with the nevela command throughout: nevela new, nevela dev, nevela resource and the rest, where they said pnpm create nevela, php nevela … and php artisan nevela:…. The longer forms still work and are listed once, under “Without the nevela command”.

0.5.0 - 2026-10-06

Users, roles and permissions

Added

  • Roles and permissions, on Grit’s model. A permission is feature.action (products.view, users.edit), every resource brings its four, and a role is a set of them. An app starts with three roles: ADMIN (everything), EDITOR (every resource) and USER (nothing beyond their own account). Laravel checks the permission on every request: $user->can('products.view'), Gate::authorize(), @can and can: middleware all work.
  • A Users screen: add, edit, switch off, sign out everywhere and delete, with search and filters by role and status.
  • A Roles screen: make roles and tick what each allows, on a grid of every permission there is. A section can be granted whole, including what is added to it later.
  • The dashboard hides what the signed-in person can’t use: resources they can’t view leave the sidebar, and buttons appear only with the matching permission.
  • Three rules on top of the permissions, enforced by Laravel: nobody hands out more than they hold, nobody changes an account that may do more than they may (so only an administrator changes an administrator’s), and the last administrator can’t be removed, switched off or demoted.
  • Switching an account off: it is kept, signed out everywhere, and refused at sign-in whichever way it comes.
  • A new app starts with ten sample users beside the administrator: two editors and eight users, one switched off. --no-sample-users leaves them out, and nevela user --sample adds them to an app that has none. They are never made in production.
  • nevela user --role=. The first account in an app is its ADMIN.
  • Permissions of your own, in config/nevela.php under permissions.

Changed

  • A generated policy asks for the resource’s permission, where it used to return true. Existing policies are your files and are not touched.
  • Someone who signs up gets the USER role (auth.default_role, which was unset). Opening sign-up no longer opens your data.
  • An account made with nevela user after the first, without --role and without being asked, is a USER. It used to be able to do everything, as every account could.

Upgrading

  • Run nevela migrate after nevela upgrade. Every user the app already has becomes an ADMIN, so nobody loses access; give people narrower roles from the Users screen. Until the migration runs, everyone can still do everything.
  • Your policies still say return true. To put a resource under permissions, change its policy to return $user->can('products.view'); and so on. See “Upgrading an app from before 0.5.0” in the docs.

Fixed

  • A request through the dashboard’s /api route with no session was answered 500 when the browser hadn’t asked for JSON. It is answered 401.

0.4.3 - 2026-10-06

nevela update did nothing under pnpm 11

Fixed

  • nevela update did nothing for a nevela command installed with pnpm 11, and said it had worked. pnpm 11 keeps a global package’s files in its store, so the command took its own install for an npm one and updated a different copy. It now goes by the folder the command was started through as well.
  • nevela update installs the version it found by number. pnpm holds a version back for a day after release when asked for @latest, so within that day it installed the previous one.
  • After updating, nevela update asks the nevela command for its version. If that is still the old one, it says so, and exits with an error, instead of reporting success.
  • The notice about several installed copies shows each copy’s version and tells you to remove the older ones. It used to say to keep the first on the PATH, which could be the oldest.

0.4.2 - 2026-10-06

The name drawn large, and nevela new asks for a name

Added

  • The name, drawn large, at the top of nevela new, nevela update and nevela: the block letters the Laravel installer and Grit use, in a gradient from blue through indigo to pink. It uses whatever colours the terminal has, and stays one plain line in a narrow terminal or when the output goes to a file.
  • nevela version works anywhere, not only inside an app. It shows the command’s version and how it was installed, and inside an app, the app’s version beside it.
  • nevela on its own lists what the command can do. It used to start creating an app. pnpm create nevela on its own still does.
  • nevela version and nevela update say so when the command is installed more than once (say with npm and with pnpm), list where, and print what removes the extra copy. The shell only ever runs the first, so updating another looked like an update that did nothing.

Changed

  • nevela new without a name asks “What is the name of your app?”, and asks again when the answer can’t be used (empty, capitals or spaces, or a folder that already exists) instead of stopping.
  • nevela update reads like Grit’s: the current version, “Checking npm for the latest release”, then “Already on the latest version” or the update.

Fixed

  • On Windows, every mistake the installer reported straight after starting ended in a crash inside Node (Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)) instead of exiting cleanly: nevela new with no name where nobody could be asked, a name that can’t be used, a folder that already exists. The installer checks npm for a newer version first, and Node on Windows crashes when a program exits just after a fetch(). It no longer uses fetch().

0.4.1 - 2026-10-05

Upgrading to 0.4.0 broke next build

Fixed

  • Upgrading an app to 0.4.0 left components/auth/sign-in-form.tsx behind, and it no longer compiled, so next build failed. An upgrade used to leave a file in place when the template dropped it. It now removes such a file when you never changed it, after copying it to the backup, and upgrade --undo brings it back. A file you changed is still always kept. An app already upgraded with 0.4.0 has that one file removed by the next upgrade.

0.4.0 - 2026-10-05

Full authentication: two-factor, passkeys, emailed links

Added

  • Full authentication, with Flare’s screens backed by Laravel. Password sign-in is joined by:
    • Two-factor: a code from an authenticator app or by email after the password, with ten backup codes.
    • Passkeys: Face ID, Touch ID, Windows Hello or a security key, with no password to type.
    • Emailed sign-in links and codes.
    • Forgot and reset password, and changing it from the account page.
    • Email verification, by a six-digit code or the link that carries it.
    • Sign-up, switched off until you set NEVELA_REGISTRATION=true. A generated policy lets every signed-in user do everything until you tighten it, so open sign-up on an untouched app would be an open door.
  • Account pages at /dashboard/account: profile, password, security and devices.
  • A profile picture, optimised with the image pipeline’s avatar profile: a 400×400 square with an 80×80 thumbnail.
  • A list of the devices signed in to an account, each with its browser and address, and signing them out. New apps get a NEVELA_PROXY_SECRET shared by the dashboard and the API, so that list can’t be dressed up by someone calling the API directly.
  • auth settings in config/nevela.php switch each method on or off. nevela generate writes them to apps/web/lib/auth-config.ts, so the screens offer only what Laravel will accept.
  • In development, emailed codes and links are also printed in the terminal running nevela dev, because the default mailer sends nothing.

Changed

  • Sign-in attempts are limited to ten a minute per account, not six a minute per address. The dashboard’s server makes these calls, so every person arrived from the same address and shared one limit.
  • A wrong password now answers 401 with code: INVALID_EMAIL_OR_PASSWORD. It was a 422 validation error.
  • GET /auth/me also returns emailVerified, twoFactorEnabled, the avatar, and which device is asking.
  • The package now requires lbuchs/webauthn, which checks passkey signatures.
  • Run nevela migrate after upgrading: there are new tables for two-factor and passkeys, and columns for the profile picture and a device’s browser.

Fixed

  • Signing out did not remove the cookie on a production build served over plain http, because a cookie marked Secure can only be removed by one that is also marked Secure.

0.3.0 - 2026-10-04

update and upgrade are two commands

Changed

  • Breaking, for the nevela command only: update and upgrade are now two commands, the same two Grit has. nevela update, from anywhere, updates the nevela command itself. nevela upgrade, inside an app, brings that app to the latest Nevela, which is what update did before. Inside an app, php nevela update, pnpm nevela update and npx create-nevela update still upgrade the app, so instructions written for older versions keep working.
  • The artisan command is nevela:upgrade. nevela:update is kept as an alias.

Added

  • nevela update updates the installed command with the package manager that installed it: npm, pnpm, yarn or bun.
  • The command’s help leads with the short forms: npm install -g create-nevela once, then nevela new my-app, nevela dev, nevela upgrade.
  • Grit’s and Flare’s ways of writing a field are understood: image:file:image, image:file:[image], category:belongs_to:Category and status:enum:draft|live mean the same as image:image, category:belongsTo(Category) and status:enum(draft|live).

0.2.1 - 2026-10-04

nevela update stopped short of 0.2.0

Fixed

  • nevela update stopped short of 0.2.0 on every app created so far. Their composer.json asks for "nevela/laravel": "^0.1", and below 1.0 that range means 0.1.x only, so Composer kept the old version and the command asked for a manual edit. The update now moves the range to the one that has the newest release (^0.2) and says that it did. From an app on 0.1.x, use npx create-nevela@latest update: the fix is in the installer, which runs before the app’s own older code.

0.2.0 - 2026-10-04

Relationships, images and files

Added

  • Relationships. category:belongsTo(Category) links a record to one of another resource. It generates the foreign key, the check that the record exists, $product->category and $category->products, and in the dashboard a picker that searches, the related name in tables, and a parent’s page listing its children. Deleting a parent that records are required to belong to answers 409 with how many there are; an optional link is cleared instead.
  • Image fields, optimised on upload the way Grit does it. image:image takes a picture, turns it the right way up, removes its metadata, scales it to fit, picks the format from the pixels (WebP; lossless when there is transparency to keep) and makes named renditions beside it. A 1.2 MB 4000×3000 photo is stored as 85 KB, with a 22 KB thumbnail. The original is kept privately.
  • Image profiles in config/nevela.php: default, product, avatar and cover, and your own. A field names one with image:image(product).
  • File fields for anything else: manual:file(pdf|document). The contents are checked against what the field accepts, and files a browser would run are never stored.
  • PUT /api/_nevela/uploads/{Resource}/{field} and GET /api/_nevela/files/{key}. A record’s API response carries a file’s address, dimensions and renditions beside its key, as <field>File.
  • php nevela seed fills relations from the records that exist and image fields with placeholder pictures, and names categories like categories.
  • The dashboard’s upload box, thumbnails and relation picker now work against Laravel, through a new /api/… route in the web app that passes the browser’s reads and uploads on with the person’s token.
  • Three guides in the docs: Build a shop, Relationships, and Files and images.

Changed

  • php nevela update says when the new version has migrations that have not been run. This one has: the table that records uploads. Run php nevela migrate after updating.

Fixed

  • Any request body over 16 KB failed under php artisan serve on Windows: Laravel starts PHP there without the temporary folder’s location, so PHP had nowhere to buffer it. Nevela now passes it through.

0.1.5 - 2026-10-04

A hydration mismatch on every full page load

Fixed

  • The dashboard reported “A tree hydrated but some attributes of the server rendered HTML didn’t match the client properties” on a full page load, with a different radix-… id on each account menu. The React bundled with Next.js 16.0.4 loses a component’s place in a list when its code arrives a moment after the page starts up, so every id beneath it comes out different in the browser. The dashboard now uses Next.js 16.3.8, which has the fix. nevela update moves an existing app to it; run the install command it prints afterwards.
  • With the device in dark mode and the dashboard’s theme left to follow it, the page the browser built differed from the one the server sent, and React threw the server’s away and rendered the dashboard again. The theme button now starts from what the server sent and switches straight after.

Security

  • Next.js 16.0.4 is marked by its maintainers as having a security vulnerability (CVE-2025-66478). 16.3.8 is a patched version.

0.1.4 - 2026-10-04

Updates that back up, undo, and run from any shell

Added

  • create-nevela --fast leaves out Laravel’s development packages for a quicker install.
  • nevela update works from any shell and on an app of any age: npx create-nevela update, pnpm nevela update, or nevela update after npm install -g create-nevela. It repairs what stops Composer from updating an older app (an exact version pin, or a package installed from the app’s own folder), then updates the package and the dashboard. The same goes for nevela dev, status, resource and the rest.
  • The dashboard’s record, apps/web/.nevela.json, now holds a fingerprint of every template file, so an update knows exactly which files you changed without downloading anything to compare.
  • php nevela update backs up every file before replacing it, saves the new version of any file you had changed to .nevela/incoming/ for comparison, and records what it did in the history.
  • php nevela update --undo puts the dashboard back as it was before the last update.
  • php nevela status -v lists the dashboard files you have changed.

Changed

  • Creating an app is about three times faster on Windows: roughly 2m 30s instead of 7m 40s on the machine it was measured on, and about 1m 35s with --fast. Laravel’s “optimized autoloader” is turned off in a new app, because building it made antivirus software scan all 9,000 freshly unpacked files; Laravel, Sanctum and Nevela are installed in one Composer run; and the setup steps share one Laravel start-up. Use composer install --no-dev --optimize-autoloader in production.
  • create-nevela fetches and runs its own newest version when the package manager hands it an older one, which pnpm does for a few hours after each release.
  • php nevela update gets the dashboard from npm, and from the release tag on GitHub when npm does not have the version yet.
  • The installer shows package-by-package progress during the long step, and prints commands in the form that works in the shell it was run from.

Fixed

  • php nevela update failed with “php: command not found” in Git Bash on Windows with Laravel Herd, where PHP is php.bat. The commands above work there.
  • php nevela update stopped at the dashboard step when a release was on Packagist but not yet on npm.

0.1.3 - 2026-10-04

php nevela status, and a dev server that finds a free port

Added

  • php nevela status: check the app in one command. It shows the Nevela version, migrations run and pending, how many people can sign in, each resource’s record count, and whether the dashboard is reaching this app’s API. Problems are marked with the command that fixes them.
  • php nevela version.
  • php nevela dev now runs the API and the dashboard itself, and checks the API’s port first. If another program has port 8000 it uses the next free one and points the dashboard at it.
  • php nevela resource … --seed fills the new resource with records in the same command.
  • GET /api/_nevela/ping, which identifies a Nevela app and which one it is.

Changed

  • New apps start with php nevela dev. They no longer get scripts/dev.mjs, which always used port 8000. php nevela update points an existing app’s dev script at php nevela dev.

Fixed

  • Sign-in failed with only “Sign-in failed. Try again.” when another program was already using port 8000, because the dashboard was talking to that program. The message now says so, and php nevela dev avoids it.

0.1.2 - 2026-10-04

php nevela, from the top of the project

Added

  • php nevela <command> from the top of the project, so there is no cd apps/api first: php nevela resource …, php nevela seed …, php nevela user, php nevela update, php nevela dev. The file is written and kept current by nevela:generate.
  • php nevela resource creates the table too. On the artisan command that is the new --migrate option.
  • php artisan nevela:update: update an existing app in one command. It updates nevela/laravel, regenerates, and brings the dashboard files you have not changed up to the new version. Files you changed are kept and listed. --check shows what would change.
  • New apps record which dashboard version they are on, in apps/web/.nevela.json.
  • create-nevela says when a newer installer exists and prints the command to use it. pnpm can serve an older one for about a day after a release.

Fixed

  • Generated files could be written with Windows line endings when the package itself was checked out that way.

0.1.1 - 2026-10-04

An installer that asks no questions

Added

  • create-nevela --bundled-package: use the copy of nevela/laravel inside the installer instead of the release on Packagist.

Changed

  • create-nevela asks no questions. A new app starts with a starter account, admin@example.com / password, in its local database, shown at the end and in the app’s README.
  • create-nevela is faster: the dashboard’s packages install while Composer creates the Laravel app, and Sanctum and Nevela are installed in one Composer run instead of two.
  • New apps no longer get a routes/api.php; Nevela registers its own routes. Run php artisan install:api if you want one.
  • New apps install nevela/laravel from Packagist when a release matching the installer’s version exists, instead of always carrying a copy in packages/nevela-laravel.

Fixed

  • Creating the first user from inside create-nevela failed with “The name field is required” on Windows. The installer no longer asks; it creates the starter account itself.
  • In a narrow terminal the installer left a half-finished progress line above each completed step.
  • On Windows, create-nevela wrote the package constraint as an exact 0.1 instead of ^0.1, so composer update would not have picked up later 0.1.x releases.

0.1.0 - 2026-10-03

The first release

Added

  • pnpm create nevela my-app: create a new app, a Laravel API and a Next.js dashboard installed and connected, with one command.
  • php artisan nevela:user: create someone who can sign in to the dashboard.
  • The MIT license, and nevela/laravel published from its own repository so Composer can install it.
  • php artisan nevela:resource: describe a resource once and generate its Laravel model, migration, form request, API resource, controller, policy and routes.
  • php artisan nevela:generate: regenerate from the descriptors. Only code between the nevela:generated markers is rewritten; a file edited inside its markers is skipped and reported.
  • php artisan nevela:seed: fill a resource with plausible records and print how long it took.
  • A REST API in Flare’s format: list with paging, sorting, search and filters, read, create, partial update, replace, delete and stats, with validation errors reported per field.
  • Token sign-in with Laravel Sanctum: POST /api/auth/token, GET /api/auth/me, DELETE /api/auth/token.
  • apps/web: Flare’s Next.js dashboard backed by the Laravel API, with sign-in, resource tables, forms, detail pages, import and export.
  • Web files generated from Laravel: the Flare descriptor, the resource registry and the dashboard pages for each resource.
  • A documentation site in apps/docs, with a home page, search, light and dark themes and the current version in the header.
  • This changelog and a release script, pnpm release.
  • CI: package tests on PHP 8.3 and 8.4, a generate, migrate and seed run in the Laravel app, a type-check and build of the web app, and a new app created with create-nevela and built.