Files

Pascal Hartig f1abd8a4a4 Update bump binaries

Summary: Update pre-compiled binaries in the repo by running `stack build` on Linux and MacOS.

Reviewed By: nikoant

Differential Revision: D21301515

fbshipit-source-id: f3b648c03a4ec7c680c88574caa3f4abbe5e0fe0

2020-04-29 06:34:58 -07:00

.gitignore

Move bump to project folder

2019-01-24 03:42:12 -08:00

bump.hs

Fix doc path

2020-04-29 06:34:58 -07:00

package.yaml

Update bump binaries

2020-04-29 06:34:58 -07:00

README.md

Bump version number

2020-02-03 06:55:32 -08:00

stack.yaml

Update bump dependencies

2019-09-26 06:44:18 -07:00

README.md

bump

A small script for changing version numbers automatically.

Usage

Requires stack to be installed.

./bump.hs --help

Alternatively, use the pre-checked-in binaries from the superfolder through bump.sh.

To bump a release version, just pass the new version number.

bump 1.2.3

To bump to a snapshot release, run with --snapshot:

bump --snapshot 1.2.4-SNAPSHOT

Building

To build the native binaries, run

stack build

The binary is then placed in .stack-work/install/x86_64-osx/**/bin/bump.

To cross-compile for Linux (required for internal CI), run

stack docker pull
stack build --docker

This is a moving target, but if you don't end up with a static binary, add ghc-options: -optl-static -optl-pthread -fPIC to your executables section.

The binary can get quite large. Enabling split objects in your global config can be quite effective in reducing it:

~/.stack/config.yaml:

build:
  split-objs: true