sinhyeok / semver-ci Goto Github PK

https://docs.rs/env_logger/latest/env_logger/

• The new prerelease command replaces the previous release command functionality

Clone before version and tag commands on Github Actions

• Run git fetch --tags to fetch tags even when git depth is not deep enough to fetch the last tag

-dev.${short_commit_sha}

Input:

• positional
  • branch name
• named
  • major: regex for major scope
  • minor: regex for minor scope
  • patch: regex for patch scope

Output:

• major | minor | patch

To run semver-ci container on GitHub actions, git cli is required to checkout code base.

Automatically generate release notes by setting the --generate-release-notes option when running the release command

• Let's try GitLab compare api

Add release_notes command
- The reason for separating the feature into another command is that the release command only works with a rest api call, while git is required to create release_notes.

• Previously, unsupported error occurred in main/master branch

As-is

Format

v0.7.0-dev.{COMMIT_SHORT_SHA}
v0.7.0-rc.{COMMIT_SHORT_SHA}

Example

# dev version
v0.7.0-dev.s90d8rfg
v0.7.0-dev.hf7r93qd

# rc version
v0.7.0-rc.fr31234t
v0.7.0-rc.gy2ertyh

To-be

Format

v0.7.0-dev.{INCREMENTAL_NUMBER}.{COMMIT_SHORT_SHA}
v0.7.0-rc.{INCREMENTAL_NUMBER}

Example

# dev version
v0.7.0-dev.1.hf29308w
v0.7.0-dev.2.eght0219

# rc version
v0.7.0-rc.1
v0.7.0-rc.2

Currently the semver-ci get it as a --previous-tag argument in the release command, but I need a way to omit the argument and automatically find previous versions or easily find previous references.

• Use GitLab list releases api

이슈

gitlab project 내 v1.9.0, v1.10.0, v1.11.0 버전이 있을 때, last tag를 v1.9.0 으로 받아와 신규 버전을 v1.10.0-rc.COMMIT_SHA로 생성합니다

원인

https://github.com/Sinhyeok/semver-ci/blob/main/src/git_service.rs#L35
last version을 가져올 때, string 비교를 하기 때문에, 큰 값을 가져오는 것이 아닐까 싶습니다!

Add a common github action for handling upcoming versions such as minor, patch, majer, etc.

Input:

• tag name

Output:

• tagged git ref

Result:

• tag and push a git tag to origin

• tag and push git tag to origin
• from last release candidate version

• Add "x86_64-unknown-linux-gnu" cargo target
• Add os to container image tag
  • v0.2.0 + v0.2.0-alpine, v0.2.0-debian