semantic-release / semantic-release/commit-analyzer

Support flexible tag format: `VariableString-${version}`

Open
#671 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
448
Forks
82
Avg merge
17h 41m
Merged PRs (30d)
4

Description

[semantic-release] › ℹ Running semantic-release version 24.0.0

I do expect this kind of tag format x.y.z+myCompany-${version} where semantic version ${version} does not care about prepend string x.y.z+myCompany- and then ${version} is continuously incremented based on last commit msg :

  • 25.1+myCompany-1.0.0
  • 25.1+myCompany-1.0.1
  • 25.2.1+myCompany-1.1.0
  • 25.2.1+myCompany-1.1.1
  • 25.2.1+myCompany-2.0.0
  • 25.3.0+myCompany-2.1.0

However and by default, each new x.y.z+myCompany- makes actually ${version} to restart from 1.0.0:

  • 25.1+myCompany-1.0.0
  • 25.1+myCompany-1.0.1
  • 25.2.1+myCompany-1.0.0
  • 25.2.1+myCompany-1.1.0
  • 25.2.1+myCompany-2.0.0
  • 25.3.0+myCompany-1.0.0

I had a look to Conventional Changelog and commit and tag version to find a way customize this default behavior ... but did not find a lead.

Any advice highly appreciated.
Thx

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by reviewing the tag examples and reproducing the current reset behavior with semantic-release 24.0.0; done would mean the requested version sequence is supported without restarting after a prefix change.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.