1.0.0 Beta 10 can have members register through XenForo's own registration service, so another add-on's reaction to a registration happens for them.
Nothing from Beta 9 has changed its name or its behaviour, and there is no upgrade step: upload the files and upgrade as usual.
New
Registration through XenForo's service. seeder:run User -p registered=1, or UserFactory::registered(), saves each member through XenForo's registration service, so an add-on that extends it - to record the browser or the country a member signed up from, say - does so for seeded members as well. XenForo itself mails and alerts nobody: its mail, welcome message and trophies are off for the save. The forum's registration setup decides whether a member is valid or awaiting confirmation or approval, unless moderated() or unconfirmed() says which, and a member the forum's options ask a date of birth or a location of is given one.
The request a registration arrives on. registered(['REMOTE_ADDR' => '203.0.113.7', 'HTTP_CF_IPCOUNTRY' => 'AU']) sets the address and headers XenForo's request carries during the save. Context::withRequest() does the same for any code of your own, and puts the real request back afterwards, even when that code throws.
Worth knowing
registered=1 runs whatever other add-ons do on a registration, which can include sending the member's details out of the forum. The seeder says so before it starts.
It is not in seeder:validate's sample, for that reason.
XenForo's spam check is not run: the registration form runs it, not the service.
The approval queue shows the address from the member's registration in the IP log, which is where a registered member's address goes.
Beta 9 given registered=1 makes the members the ordinary way, lists the parameter as ignored and exits with 1. The README marks both additions since 1.0.0b10