98c3913b62
Summary:
Original commit changeset: 7c72d541f9f2 / D26723361 (4a71a5abd1)
Pods are not released yet(?) and nor are our npm packages when our CI runs for the first time after pushing a release to GH, which would make the job always fail. Backing out of the process for now.
For the npm package, dependabot will automatically take care of it. The gradle properties / podfile will remain manually bumps for now.
Reviewed By: nikoant
Differential Revision: D27764997
fbshipit-source-id: db505c2d0882f74b2f5d4e0454463a5e08501a90
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