Fix update-docs workflow not triggering on releases#3968
Merged
JakeSCahill merged 1 commit intomainfrom Feb 6, 2026
Merged
Conversation
1c18409 to
8c8a6ad
Compare
mmatczuk
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The update-docs workflow wasn't firing on releases. Turns out we were using
publishedwhich fires for prereleases too, then filtering them out with anifcondition. But if the release was marked as a prerelease at any point, the job just silently skipped.Switched to
releasedwhich only fires for actual releases (not prereleases), so we don't need the manual filtering anymore.Also added a job to trigger the cookbook example tests in rp-connect-docs when we release.
Changes:
publishedtoreleasedevent typetest-cookbook-examplesjobTested with
act- all three jobs run as expected.