gistfile1.txt

BIN = ./node_modules/.bin
SRC = $(wildcard src/*.coffee)
LIB = $(SRC:src/%.coffee=lib/%.js)

build: $(LIB)

lib/%.js: src/%.coffee
  @mkdir -p $(@D)
  @$(BIN)/coffee -bcp $< > $@

test: build
  @$(BIN)/mocha -b specs

clean:
  @rm -f $(LIB)

install link:
  @npm $@

define release
  VERSION=`node -pe "require('./package.json').version"` && \
  NEXT_VERSION=`node -pe "require('semver').inc(\"$$VERSION\", '$(1)')"` && \
  node -e "\
    var j = require('./package.json');\
    j.version = \"$$NEXT_VERSION\";\
    var s = JSON.stringify(j, null, 2);\
    require('fs').writeFileSync('./package.json', s);" && \
  git commit -m "release $$NEXT_VERSION" -- package.json && \
  git tag "$$NEXT_VERSION" -m "release $$NEXT_VERSION"
endef

release-patch: build test
  @$(call release,patch)

release-minor: build test
  @$(call release,minor)

release-major: build test
  @$(call release,major)

publish:
  git push --tags origin HEAD:master
  npm publish

I know this is two years old but I just wanted to point out that you can bump the version number easily with npm version which also automatically creates a git tag if your package has a git repo. So you can get rid of the release macro and do this instead

release-patch: build test
  npm version patch

release-minor: build test
  npm version minor

release-major: build test
  npm version major