standard-version is deprecated, switch to in-place replacement or release-please?

Open
#1,105 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
release, tooling

Research direction

No file, test, or entry point is named. First locate where standard-version is configured and invoked, then compare the proposed replacement options before selecting one; done is not defined because the issue leaves the replacement undecided.

Written by the indexing model from the issue text.

Description

feature request need eyes

Description:
Support for standard-version was dropped about 18 months ago.
Someone made a fork and has pledged to maintain it: https://github.com/absolute-version/commit-and-tag-version
It claims full compatibility and should beeasy to switch to.

Alternative is to take this chance to switch to something else, release-please has been mentioned, and there's also things like https://github.com/semantic-release/semantic-release that even handle the publish of the package.

Justification:
Using deprecated, unmaintained packages is always a risk

Are you willing to submit a PR?
No, sorry, just saw that this is deprecated and wanted to let the people know who have to work with it 😉

Dominant language
TypeScript
Stars
1.7k
Forks
438
Avg merge
27d 8h
Merged PRs (30d)
1

Getting set up

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.

More from actions/stale

All issues in actions/stale

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.