Skip to content

Commit

Permalink
2.1.2
Browse files Browse the repository at this point in the history
  • Loading branch information
@evenstensberg
evenstensberg committed Apr 30, 2018
1 parent 8c9b895 commit bd16440
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion package-lock.json
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "webpack-cli",
"version": "2.1.1",
"version": "2.1.2",
"description": "CLI for webpack & friends",
"license": "MIT",
"preferGlobal": true,
Expand Down

7 comments on commit bd16440

@DanielRuf
Copy link
Contributor

@DanielRuf DanielRuf commented on bd16440 May 2, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems semantic-release tries to publish this as 2.1.0 tag which does already exist which is probably due to the Travis cache.

@evenstensberg
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but it should notice existing tags, shouldn't it?

@DanielRuf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right but it still seems the cached files tried to push 2.1.0 instead of 2.1.2 according to the failing Travis test.

@evenstensberg
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any idea of how to fix that? Just brought it up in the slack channel

@DanielRuf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mh, I might have to setup a separate GitHub repo with the same integration and Travis configuration to find a solution.

@DanielRuf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have an issue here so I can track this and contribute to it if possible?

@ematipico
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can create it if you need it :)

Please sign in to comment.