Context
As part of implementing automated patch releases on every merge (#1539 item 2), we currently release on every merge to dev regardless of what files changed.
Consideration
We may want to skip auto-releases for commits that only touch:
- Documentation (
mkdocs/**, *.md)
- CI configuration (
.github/**)
- Other non-code files
Tradeoffs
Pros of filtering:
- Fewer unnecessary releases
- Version numbers more meaningful (each bump = actual code change)
Cons of filtering:
- More complex workflow logic
- Risk of missing releases if filter is too aggressive
- Documentation fixes sometimes matter for users
Decision
For now, we release on every merge. This issue tracks whether we should add filtering in the future.
Related
Context
As part of implementing automated patch releases on every merge (#1539 item 2), we currently release on every merge to
devregardless of what files changed.Consideration
We may want to skip auto-releases for commits that only touch:
mkdocs/**,*.md).github/**)Tradeoffs
Pros of filtering:
Cons of filtering:
Decision
For now, we release on every merge. This issue tracks whether we should add filtering in the future.
Related