Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Commit

Permalink
Prepare release v3.3.0-dev.2
Browse files Browse the repository at this point in the history
  • Loading branch information
Jason Killian committed Jan 26, 2016
1 parent 3e6c8bb commit 08e0ca7
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 3 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
Change Log
===

v3.3.0-dev.2
---
* Add TypeScript peer dependency `>=1.9.0-dev` to support latest nightlies

v3.3.0-dev.1
---
* [bugfix] Correctly handle more than one custom rules directory (#928)
Expand Down
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "tslint",
"version": "3.3.0-dev.1",
"version": "3.3.0-dev.2",
"description": "a static analysis linter for TypeScript",
"bin": {
"tslint": "./bin/tslint"
Expand Down Expand Up @@ -40,7 +40,7 @@
"typescript": "next"
},
"peerDependencies": {
"typescript": ">=1.7.3 || >=1.7.0-dev.20151003 || >=1.8.0-dev || >=1.9.0-dev"
"typescript": ">=1.7.3 || >=1.8.0-dev || >=1.9.0-dev"

This comment has been minimized.

Copy link
@alexeagle

alexeagle May 27, 2016

Contributor

hey @jkillian is there a reason the last option (1.9) was never merged to master? I'd like to upgrade angular's tslint from 3.7.0-dev.2 to 3.9.0 but our shrinkwrap fails due to unmet peer dep

This comment has been minimized.

Copy link
@alexeagle

alexeagle May 27, 2016

Contributor

oh, sorry, I asked too quickly. I see the dev branch is still being released, so I just need tslint@3.10.0-dev.2
But sadly gulp-tslint doesn't support it, so my issue is there.

Sorry for the distraction.

This comment has been minimized.

Copy link
@jkillian

jkillian May 27, 2016

Contributor

Yep, no worries! Btw, let us know if you have any better ideas for publishing the tslint@next/-dev line of releases that work with the nightly TypeScript releases. Publishing them as prereleases works okay, but it ends up making semver real quirky in certain cases.

This comment has been minimized.

Copy link
@jkillian

jkillian May 27, 2016

Contributor

Here's an example of the quirkiness, where we have to enumerate every prerelease version...

},
"license": "Apache-2.0",
"typescript": {
Expand Down
2 changes: 1 addition & 1 deletion src/tslint.ts
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ import {ILinterOptions, LintResult} from "./lint";
import {loadRules} from "./ruleLoader";

class Linter {
public static VERSION = "3.3.0-dev.1";
public static VERSION = "3.3.0-dev.2";
public static findConfiguration = config;

private fileName: string;
Expand Down

0 comments on commit 08e0ca7

Please sign in to comment.