Skip to content

fix: found error with line length in a release commit (inc skip ci)Β #4594

@SSmale

Description

@SSmale

Steps to Reproduce

https://github.com/SSmale/Duux-Home-Assistant/actions/runs/21101074468/job/60685349581#step:4:1

Error log from the ci run

Manually

git commit -m 'chore(release): 2.3.3-beta.1 [skip ci]'

Current Behavior

The Problem
For a commit like:
chore(release): 2.3.3-beta.1 [skip ci]

Step-by-step breakdown:

  1. First line: "chore(release): 2.3.3-beta.1 [skip ci]"
  2. After replace: " 2.3.3-beta.1 [skip ci]"
  3. After trim: "2.3.3-beta.1 [skip ci]"
  4. semver.valid("2.3.3-beta.1 [skip ci]") β†’ null ❌

So it doesn't match and the commit is NOT ignored.

What It SHOULD Match

For proper semantic-release support, it should also strip common CI skip markers:

  • [skip ci]
  • [ci skip]
  • [skip-ci]
  • [ci-skip]
  • Potentially: (skip ci), (ci skip), etc.

Expected Behavior

Message ignored as it’s CI generated

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

No response

Context

No response

commitlint --version

Unknown

git --version

Unknown

node --version

Unknown

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions