v4.19.0

this is a nearly breaking change, but didn't seem up to the level of a major release.

If you're using ai:auth, it was storing access _tokens, and from time to time would error out and have to be reauthed.

It now uses a refresh token process. So it'll be better than that (run once, store for the long-term), but an existing access token will be broken from previous versions even if it's still valid for a while.

v3.24.0

add support for creating record types on an object and adding recordtypes to a permset.

Shoutout to @FabienTaillon for the contribution.

custom labels, drop node engine

• shane:label:add makes custom labels in local source so you don't have to do it in the ui
• drops the engine specification...seeing if people have fewer install problems with older versions of node

windows support, mdapi:pull at scale

1. fixed windows issues (was using native linux commands like rm and unzip that caused windows fails
2. mdapi:pull is now interrogating the mdapi, getting all types on an org, and making a pull for each of them using the sfdx source:retreive command

• should handle way, way more metadata (previous version was failing on retrieve AND convert)
• had to give up the --target option, so the converted source is going into your default pkgDir no matter what. Sorry.

Breaking changes from upstream, plus ui-api

Breaking changes

I had used what are now illegal short flags (-u for userprefix) on shane:org:create which wraps the sfdx command. * You now have to spell out --userprefix instead of using -u

• there is no more -v on that one

flags updates

all the flags migrated to the latest @salesforce/command flag types. Should provide better experience, it's very possible I broke something.

Because of this, I bumped this up as a major release

New stuff

the shane:uiapi topic now makes it easy to get (meta)data from the ui-api for mocking your LWC local jest tests (or whatever else you feel like doing with uiapi responses). I built these to focus on the LWC wrappers for ui-api, so they don't have all the options of REST-based ui-api.