ipfs / ipfs/aegir

feat: RC with correct version number

Open
#1,574 1 comment 1 reaction 0 assignees View on GitHub
help wanted kind/enhancement
Dominant language
JavaScript
Stars
105
Forks
62
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If I am to release a major update, I expect the release candidate to be something like

1.0.0-hash

but now the rc seems to just use the [manifest](https://github.com/ipfs/aegir/blob/fe833e3d6878594b0c972c1ca4de1b1b6e267c58/src/release-rc.js#L54C50-L54C58) version.

so I get something like

0.x.y-hash

Is the feasible to fix? I guess this would need to integrate with some semantic release library to predict the next version

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.