Skip to content

Commit

Permalink
Twitter-oss: Prepare OSS libraries for release 19.12.0
Browse files Browse the repository at this point in the history
Problem

We want to release the next versions of our Twitter OSS libraries 19.12.0
 - util
 - scrooge
 - finagle
 - twitter-server
 - finatra

Solution

Prepare libraries for their next releases.

Differential Revision: https://phabricator.twitter.biz/D413458
  • Loading branch information
David Rusek authored and jenkins committed Dec 13, 2019
1 parent acf7e01 commit 1613e30
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 2 deletions.
3 changes: 3 additions & 0 deletions CHANGELOG.rst
Expand Up @@ -7,6 +7,9 @@ Note that ``PHAB_ID=#`` and ``RB_ID=#`` correspond to associated messages in com
Unreleased
----------

19.12.0
-------

* Upgrade to jackson 2.9.10 and jackson-databind 2.9.10.1 ``PHAB_ID=D410846``

* Multiple changes have happened around query parameter retrieval in order
Expand Down
2 changes: 1 addition & 1 deletion README.md
@@ -1,6 +1,6 @@
# TwitterServer

[![Build status](https://travis-ci.org/twitter/twitter-server.svg?branch=develop)](https://travis-ci.org/twitter/twitter-server)
[![Build status](https://travis-ci.org/twitter/twitter-server.svg?branch=master)](https://travis-ci.org/twitter/twitter-server)
[![Codecov](https://codecov.io/gh/twitter/twitter-server/branch/develop/graph/badge.svg)](https://codecov.io/gh/twitter/twitter-server)
[![Project status](https://img.shields.io/badge/status-active-brightgreen.svg)](#status)
[![Gitter](https://badges.gitter.im/twitter/finagle.svg)](https://gitter.im/twitter/finagle?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
Expand Down
2 changes: 1 addition & 1 deletion build.sbt
@@ -1,7 +1,7 @@
import scoverage.ScoverageKeys

// All Twitter library releases are date versioned as YY.MM.patch
val releaseVersion = "19.12.0-SNAPSHOT"
val releaseVersion = "19.12.0"

val jacksonVersion = "2.9.9"
val jacksonDatabindVersion = "2.9.10.1"
Expand Down

0 comments on commit 1613e30

Please sign in to comment.