Commit 902d3db
Implement path-based triggers to prevent spurious publish/release (#69)
Problem: Any push to master triggered publish and release workflows,
including enhancement PRs that only changed .github/ files or documentation.
Solution: Path-based triggers that only publish when SDK code changes.
Changes:
- Created on-push-master.yml with explicit path filters for SDK files
- Updated publish.yml: added workflow_call trigger, removed push trigger
- Updated release.yml: added workflow_call trigger, removed push trigger
Behavior after this change:
✅ SDK file changes (api.ts, package.json, etc.) → triggers publish/release
✅ Workflow changes (.github/**) → does NOT trigger publish/release
✅ Documentation changes (README.md) → does NOT trigger publish/release
This allows safe merging of workflow enhancements, config updates, and
documentation without triggering package releases.
Refs: Multi-version-POC-blockers.md Phase 1
Co-authored-by: Genevieve Nuebel <genevieve.nuebel@mx.com>1 parent b9c0358 commit 902d3db
3 files changed
Lines changed: 29 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | | - | |
6 | 4 | | |
7 | 5 | | |
8 | 6 | | |
| 7 | + | |
9 | 8 | | |
10 | 9 | | |
11 | 10 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | | - | |
6 | 4 | | |
7 | 5 | | |
| 6 | + | |
8 | 7 | | |
9 | 8 | | |
10 | 9 | | |
| |||
0 commit comments