I'm beginning to get annoyed with the unnecessary diff in every PR for API docs
And it only makes sense to re-generate docs for each new release
So, I propose to add this to the version step for changesets instead of pre-commit, and let it churn these changes on merge to main only, so that the docs only change per reach release anyways (which will be even better, because they will reflect the actually released API, not the current iteration which may not yet be published)
I'm beginning to get annoyed with the unnecessary diff in every PR for API docs And it only makes sense to re-generate docs for each new release
So, I propose to add this to the
versionstep for changesets instead of pre-commit, and let it churn these changes on merge to main only, so that the docs only change per reach release anyways (which will be even better, because they will reflect the actually released API, not the current iteration which may not yet be published)