Supporting the `expo prebuild` workflow

[mikehostetler]

Topic and scope of discussion

How would you summarise and scope the issue?

I've upgraded to Expo SDK 44 and have converted all of my changes inside the /ios and /android folders of my Expo Bare project over to using config plugins. I do commit my /ios and /android folders to source, but I only make changes to them using the new expo prebuild command.

My release workflow is:

// Increment a patch version
% npx standard-version

// Undo standard version's commit and delete the GIT tag 
% git reset --soft HEAD^
% git tag -d $TAG

// Re-run rebuild, carrying the versions in app.json into native code
% expo prebuild

// Re-stage latest GIT changes
% git add ...
% git commit

% git tag $TAG
% git push --follow-tags origin master

Motivation

Why should we have this discussion?

1. Thoughts on adding a flag to standard-version that skips the commit step, so I don't have to undo it?
2. How do we want to take expo prebuild into account? Should I use native bumpers, or continue using prebuild?

Additional context

Can you further explain the purpose of this discussion? E.g., screenshots or real-world examples.

See release workflow example above

[mitramejia]

Maybe you could use standard-libary config to skip the commit step