feat: release docs on release and not CI

[jacqueswho]

Reasons for making this change

fixes #2847

Checklist

• [ ] I'm updating documentation
  • [ ] I've checked the rendering of the Markdown text I've added
• [ ] I'm adding or updating code
  • [ ] I've added and/or updated tests. I've run npm run test:update to update snapshots, if needed.
  • [ ] I've updated docs if needed
  • [ ] I've updated the changelog with a description of the PR
• [x] I'm adding a new feature
  • [ ] I've updated the playground with an example use of the feature

[jacqueswho]

@epicfaace I was thinking that. But this way if any needs to release the docs early they can without waiting for code changes. There could be a scenario when there might just be doc changes and no code changes. Then to wait for a release could be troublesome. What do you think? By allowing to call the action on request as an option

[epicfaace]

@epicfaace I was thinking that. But this way if any needs to release the docs early they can without waiting for code changes. There could be a scenario when there might just be doc changes and no code changes. Then to wait for a release could be troublesome. What do you think? By allowing to call the action on request as an option

Makes sense! Can you add a section to https://react-jsonschema-form.readthedocs.io/en/latest/contributing/#documentation that describes how docs deploy work and how to trigger a manual deploy?

[jacqueswho]

@epicfaace I cant merge

[heath-freenome]

@jacqueswho looks like the docs workflows never reported in?

[heath-freenome]

@epicfaace Do you concur this is ready to merge?

[heath-freenome]

@jacqueswho We really need to get stable built. What is missing?

[epicfaace]

Agree, this looks good to me.