Restrict Premature Documentation

[khajavi]

Currently, when we push a PR that contains documentation changes and it gets merged into the main branch, the new documentation site is automatically published.

This causes the documentation site to be updated with features that have not been released yet, resulting in premature publication.

We should change the CI so that the documentation is published only on release events or via manual triggering.

[MalathiBalaraman31]

@khajavi Hi
I’d like to work on this issue if it’s still available.

My understanding:

• Docs are currently published on every merge to main
• This causes unreleased features to appear on the docs site
• The goal is to publish docs only on releases or via manual trigger

Proposed approach:

• Update the documentation CI workflow to trigger only on:
  • release events (e.g. published)
  • and/or workflow_dispatch
• Ensure existing behavior is preserved for maintainers who want manual control
• Update documentation (if needed) to clarify the new publishing flow

Please let me know if this approach aligns with your expectations before I start .

[khajavi]

@MalathiBalaraman31 It seems to be okay!