Skip to content

ci: narrow publish trigger to root RELEASES.md only#552

Merged
Nelson-PROIA merged 1 commit into
mainfrom
ci/narrow-publish-trigger-to-root-releases
May 22, 2026
Merged

ci: narrow publish trigger to root RELEASES.md only#552
Nelson-PROIA merged 1 commit into
mainfrom
ci/narrow-publish-trigger-to-root-releases

Conversation

@Nelson-PROIA
Copy link
Copy Markdown
Contributor

Summary

The publish workflow currently triggers on any **/RELEASES.md change in main. Since the workflow builds a single bundled mistralai wheel from root pyproject.toml (with sub-packages as source-included), only the root RELEASES.md changing reflects a new release.

Sub-package RELEASES.md changes (packages/azure, packages/gcp) shouldn't trigger publish runs since they don't produce a new bundled wheel.

Fix

```diff
push:
branches:
- main
paths:

  •  - \"**/RELEASES.md\"
    
  •  - RELEASES.md
    

```

Effect

  • Azure/gcp regen merges no longer trigger spurious publish workflow runs that wait at the env gate
  • Only meaningful releases (root RELEASES.md bump) trigger publish

The publish workflow builds a single bundled mistralai wheel from root
pyproject.toml that includes the sub-packages as source. Only the root
RELEASES.md changing reflects a new release. Sub-package RELEASES.md
changes (packages/azure, packages/gcp) shouldn't trigger publish runs
since they don't produce a new wheel.
@Nelson-PROIA Nelson-PROIA merged commit 6fc2ef0 into main May 22, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants