Releases

1Request

Secret key in X-Blipit-Key. Body up to 2 MB: version (required, up to 256 characters), commit and previous_commit (git shas, 7 to 40 hex), repo (owner/name), commits (optional list from git log: sha, message, author, changed files, up to 250). Without previous_commit Blipit keeps the commits after the last release's commit, or just the head for a first release.

curl https://in.blipit.io/api/v1/releases \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <secret key>" \
  -d '{"version":"shop@1.4.2","commit":"9fceb02a","previous_commit":"3a1c7f0d","repo":"acme/shop"}'

2Responses

200 {version, commits, source (github, cli or null), previous_commit, warning?}. The warning says when the GitHub lookup failed and the CLI commits were used. 400 for a bad version, sha or repo. 401 unknown key, 403 public key.

Good to know

• repo may only be owner/name; anything with @, //, .., ?, # or extra segments is refused so GitHub calls only ever reach api.github.com/repos/owner/name.
• The GitHub compare fetch has a 10-second timeout and reads changed files for the newest 30 commits.