opened 2.2

nette · May 25, 2014 · 003654d · 003654d
1 parent 9bc3678
commit 003654d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 7 deletions.
diff --git a/composer.json b/composer.json
@@ -25,10 +25,5 @@
 	"autoload": {
 		"classmap": ["src/"]
 	},
-	"minimum-stability": "dev",
-	"extra": {
-		"branch-alias": {
-			"dev-master": "2.2-dev"
-		}
-	}
+	"minimum-stability": "dev"
 }
diff --git a/readme.md b/readme.md
@@ -2,7 +2,7 @@ Nette SafeStream: Atomic Operations
 ===================================
 
 [![Downloads this Month](https://img.shields.io/packagist/dm/nette/safe-stream.svg)](https://packagist.org/packages/nette/safe-stream)
-[![Build Status](https://travis-ci.org/nette/safe-stream.svg?branch=master)](https://travis-ci.org/nette/safe-stream)
+[![Build Status](https://travis-ci.org/nette/safe-stream.svg?branch=v2.2)](https://travis-ci.org/nette/safe-stream)
 
 The Nette\Utils\SafeStram protocol for file manipulation guarantees atomicity and isolation of every file operation. Why
 is it actually good? Let's start with a simple example, where we repeatedly write the same string to the file and then read it: