Skip to content

πŸ”– branchMatchRegex 3.0.0-rc1

Pre-release
Pre-release

Choose a tag to compare

@iampekka058-s-bot iampekka058-s-bot released this 06 Nov 22:16
· 61 commits to main since this release
Immutable release. Only release title and notes can be modified.

First release candidate of the Go rewrite. Inputs stay the same, but the action now runs from an immutable container image and evaluates patterns with RE2.

✨ Highlights

  • Rewritten in Go – the Node/TypeScript implementation and bundled dist/index.js are gone.
  • Container-based action – runs from ghcr.io/michisec/branchmatchregex and is pulled automatically by GitHub Actions.
  • RE2 regex engine – predictable, linear-time matching without catastrophic backtracking.
  • Immutable releases – exact versions only; no latest, moving v3, or v3.0 tags.
  • Same inputs – patterns, path, failOnUnmatchedPattern, useWildcardPatterns, useDefaultPatterns, and branch are unchanged from v2.
  • Small runtime footprint – static Go binary in a scratch image, with only CA certificates added.

⚠️ Breaking changes

  • Linux runners only. This is a Docker container action; Windows and macOS runners are not supported.
  • RE2 instead of V8. Lookarounds ((?=...), (?<=...)), backreferences (\1), and other V8-specific regex features are not supported. Such patterns now fail with an explicit ::error::.
  • Exact version pinning required. Use a full release tag:
    uses: michisec/branchMatchRegex@v3.0.0-rc.1
    There is no moving v3 alias. Minor and patch upgrades require updating the tag.
  • GHCR image must be reachable. The container package must be public, or the consuming workflow needs package access.
  • The old v2 tag is frozen at v2.2.1 and no longer receives updates.

πŸ”„ Upgrading from v2

Change the version reference:

# before
uses: michisec/branchMatchRegex@v2

# after
uses: michisec/branchMatchRegex@v3.0.0-rc.1

No input changes are required. If you use advanced regex patterns, verify them before upgrading:

with:
  patterns: |
    feature/.*
    fix/.*
    release/v[0-9]+\.[0-9]+

Wildcard mode works as before:

with:
  useWildcardPatterns: true
  patterns: |
    feature/*
    fix/*

πŸ§ͺ Please test

This is an RC. Feedback is especially useful on:

  • existing workflows with unchanged inputs
  • wildcard patterns and useDefaultPatterns
  • patterns loaded from files and URLs
  • failOnUnmatchedPattern: false
  • regex patterns that may use lookarounds or backreferences
  • self-hosted Linux runners and GHCR access

πŸ“¦ Container image

Release images are published as:

  • ghcr.io/michisec/branchmatchregex:v3.0.0-rc.1
  • ghcr.io/michisec/branchmatchregex:sha-<full-commit-sha>

There is intentionally no latest or moving major tag. Every deployed version stays reproducible.

πŸ› οΈ Under the hood

  • Go 1.25 with github.com/sethvargo/go-githubactions and gopkg.in/yaml.v3
  • Tests ported from Jest to Go; internal/patterns and internal/runner are at 100 % statement coverage
  • CI now runs gofmt, go vet, golangci-lint, and go test -race
  • Multi-stage Docker build; runtime image is scratch
  • Repository moved to michisec/branchMatchRegex (old URLs redirect)

πŸ“ Notes

  • This release candidate is intended for validation before v3.0.0.
  • If anything breaks, please include the action version, runner OS, and the pattern configuration in the issue.

Full Changelog: v2.2.1...v3.0.0-rc1