Skip to content

ci: run tests when packages/forge or packages/git change - #705

Merged
goosewobbler merged 1 commit into
mainfrom
ci/704-forge-git-filters
Oct 23, 2026
Merged

goosewobbler merged 1 commit into
mainfrom
ci/704-forge-git-filters

Conversation

@goosewobbler

@goosewobbler goosewobbler commented Oct 23, 2026 •

Copy link
Copy Markdown
Owner

Description

packages/forge and packages/git weren't in any Detect Changes filter, so a PR touching only them ran no build, typecheck, unit or integration tests, and CI Status passed.

Both are now in the config filter. Like packages/core, a change there runs every package's tests, which is right here: version, publish and release depend on both. The step-summary row is relabelled to match.

Related Issue(s)

Closes #704

Type of Change

  • feat — New feature
  • fix — Bug fix
  • docs — Documentation change
  • refactor — Code refactoring
  • test — Adding or updating tests
  • chore — Maintenance, dependencies, tooling
  • Breaking change — Requires major version bump

Scope

  • @releasekit/version
  • @releasekit/notes
  • @releasekit/publish
  • @releasekit/release
  • @releasekit/config
  • @releasekit/core
  • CI / workflows
  • Root / monorepo

Checklist

  • Lint passes (pnpm lint)
  • Tests pass (pnpm test)
  • Typecheck passes (pnpm typecheck)
  • Documentation updated (if applicable)
  • Breaking changes noted in description

Testing Notes

actionlint and Biome are clean. Every directory under packages/ now maps to a filter. #697 also edits this workflow, on different lines.

🤖 Generated with Claude Code

RetriggerView in GreptileConfidence Score: 5/5

This PR appears safe to merge.

Summary

Adds packages/forge/** and packages/git/** to the shared config filter.

  • Forge and git changes now trigger the existing package test route.

Reviews (1) · Last reviewed commit: "ci: run tests when packages/forge or pac..." · Reviewed by Greptile

Neither package was in any change filter, so a PR touching only them ran no
build or tests. Add both to the config filter, which like core's triggers
every package's tests: version, publish and release depend on them.

Closes #704

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 7h 51m · ✅ ready to merge

Release Preview — v0.41.2 → v0.41.3

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#614) when merged:

Changelog

monorepo 0.41.2 → 0.41.3

Changed

  • run tests when packages/forge or packages/git change (#704)

All packages → 0.41.3 (sync versioning)

  • @releasekit/version
  • @releasekit/notes
  • @releasekit/publish
  • @releasekit/release

After merge — predicted release

No version escalation — this PR's changes will be included in the queued release without affecting the projected versions.

Package Standing PR This PR After merge
monorepo 0.42.0 0.41.3 0.42.0

Updated automatically by ReleaseKit

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.

CI skips every test for PRs that only change packages/forge or packages/git

1 participant