Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/trendmicro/new-release-version
https://github.com/trendmicro/new-release-version
cicd releases semver versioning
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/trendmicro/new-release-version
- Owner: trendmicro
- License: apache-2.0
- Created: 2020-10-27T02:43:57.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-04-19T13:56:28.000Z (9 months ago)
- Last Synced: 2024-06-20T06:42:44.596Z (7 months ago)
- Topics: cicd, releases, semver, versioning
- Language: Go
- Homepage:
- Size: 2.14 MB
- Stars: 5
- Watchers: 5
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# New Release Version
Forked from
[](https://pkg.go.dev/github.com/trendmicro/new-release-version/)
`new-release-version` is a simple command that will print a new patch (or minor) version for a release.
This helps in continuous delivery if you want an automatic release when a change is merged to your main branch. Traditional approaches mean the version is stored in a file that is checked and updated after each release. If you want automatic releases this means you will get another release triggered from the version update resulting in a cyclic release situation.
Using a git tag to work out the next release version is better than traditional approaches of storing it in a VERSION file or updating a project's config file.
The major and minor version of the release is determined by searching for a version identifier in a project config file, like `package.json` or `build.gradle.` See [examples](examples) for supported version files.
When you need to bump the major or minor version of your project, simply increment the version in your project's config file and commit that to your main branch.
`new-release-version -help`:
```
Usage of ./new-release-version:
-base-version string
Version to use instead of version file.
-debug
Prints debug into to console.
-directory string
Directory of git project. (default ".")
-gh-owner string
GitHub repository owner to fetch tags from instead of the local git repo.
-gh-repository string
GitHub repository to fetch tags from instead of the local git repo.
-git-fetch
Fetch tags from remote. (default true)
-minor
Increment minor version instead of patch.
-same-release
Increment the latest base version release ignoring any releases higher than the base version release.
-version
Prints the version.
```
## Install
You must have [Git](https://git-scm.com/) installed on your system in order for `new-release-version` to work.
You can install the latest from the `main` branch
go get github.com/trendmicro/new-release-version
Or install a specific version from [releases](https://github.com/trendmicro/new-release-version/releases/)
## Examples
```sh
➜ RELEASE_VERSION=$(new-release-version)
➜ echo "New release version ${RELEASE_VERSION}
➜ git tag -fa v${RELEASE_VERSION} -m 'Release version ${RELEASE_VERSION}'
➜ git push origin v${RELEASE_VERSION}
```
- If your project is new or has no existing git tags then running `new-release-version` will return a default version of `0.0.1`
- If your latest git tag is `1.2.3` and your version file is `1.2.0-SNAPSHOT` then `new-release-version` will return `1.2.4`
- If your latest git tag is `1.2.3` and your version file is `2.0.0` then `new-release-version` will return `2.0.0`
- If your latest git tag is `7.1.0` but you want to increment an older release, say `7.0.5`, use `new-release-version -base-version 7.0 -same-release` to return the next version in the `7.0` release.
## Development
### Prereqs
- [Go](https://go.dev/)
- [Git](https://git-scm.com/)
### Build
make build
### Test
make test