tree 6224906a7781df4da5c9299af88eb4660fd39b2f
parent f8c2ac92efeba1d0cea8fe7b58eaf8f4461e5a6b
author Ethan Lin <linsen458@gmail.com> 1789139522 +0800
committer GitHub <noreply@github.com> 1789139522 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJqpBpCCRC1aQ7uu5UhlAAAOuEQAGcj/JHnChGZvkIFvrIGS8Dx
 hiYWjw+NqfzNboTnzOiVcLbXKp/lp0mL7mzTEwYQgINkcICZHXgEqXMhPDygWC+e
 Q0qfxunLcq8nH6PzkvJXtGS5Mv+1GrGcGlMfz0CiLfQmlNAZWP1IqaQrccgNqpmM
 Q/pIWKnYc5CRKGxsR9n/Z7nKiBruqOw59x4ryFQ9l7Vk1l8R/u2echS/6Fnq8kTz
 hQcC6HkQl1Qq9C/A9xzFTU1Yxw3BOOLgzdw3qGup/xy9lc9xuJFkUzbpZP1JAwal
 hpPQpAQscc8RTSSo04b0pXT2yx0oaWScXZ3c8VjPqhXltgT56aabqKkcYkXRyLLV
 rn6Puv6LdMARaM0QN9/9JFWxwguIeWUef8tzjCkHK07c6qzNHdLEAswVwsMVjvgW
 5l1J/49YcYUyYT8iixJuHhhRjL0LbPauIezUEDlHFrC52GbK3MvgSdFSkI3/Qxt6
 rsJSN5YnvYMhXN4bCMiFgrxUjmESZeabrzzfsAUGyoUqMqCX4kPFws/ufvL5xsCV
 0I8mtnDh7eeGgNmKJbRs+bgoPo43JDShVzoBjGu2hD5JrIiACINRRZfE6zNm6WSu
 oRHLUgkPrrpSrhwplfLjEX62xLkn1G+pRY+yJaMCX9sjiGr4B1pW0Ps+tBuQzOhD
 DxzN0ZrJSsZ93vufEr9N
 =I6as
 -----END PGP SIGNATURE-----
 

publish_website: only publish from main, verify-only on release candidates (#24907)

The Publish Website workflow is triggered by `release: [published,
unpublished]` events. Release candidate releases (tags like
`iree-3.6.0rc20250910`) go through the same path: the candidate release
workflows create a draft prerelease, Build Release Packages fills it,
and Validate and Publish Release publishes it -- which fires the
`published` event and made Publish Website deploy the site from the RC,
overwriting whatever main had last published (losing a blogpost
recently).

Keep running the site build steps as verification, but skip the gh-pages
deployment when the run was triggered by a release candidate release.
Deployment still happens for main pushes, schedules, manual dispatches,
and stable releases.

Fixes #24764

Assisted-by: Claude Code / glm-5.3-flash

Signed-off-by: linsen <251731047+linsen458-spec@users.noreply.github.com>
Co-authored-by: linsen <251731047+linsen458-spec@users.noreply.github.com>