Skip to content

Commit

Permalink
Bump gem version 1.0.1 → 2.0.0
Browse files Browse the repository at this point in the history 
Due to b1c09e8 this is a backwards-incompatible change, and so we are
bumping the major version to adhere to semantic versioning.
  • Loading branch information
@sds
sds committed Jul 11, 2019
1 parent e81a587 commit 1d80933
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
### dev / unreleased
### Version 2.0.0 / 2019-07-11

* [#148](https://github.com/enkessler/childprocess/pull/148): Drop support for Ruby 2.0, 2.1, and 2.2
* [#149](https://github.com/enkessler/childprocess/pull/149): Fix Unix fork reopen to be compatible with Ruby 2.6
Expand Down
2 changes: 1 addition & 1 deletion lib/childprocess/version.rb
View file
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
module ChildProcess
VERSION = '1.0.1'
VERSION = '2.0.0'
end

1 comment on commit 1d80933

@sds
Copy link
Collaborator Author

@sds sds commented on 1d80933 Jul 11, 2019

Choose a reason for hiding this comment

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

Build failure in AppVeyor is due to the commit message having a Unicode character (→) in its subject line, and AppVeyor builds always including this message as an environment variable in builds.

One of the tests causes these environment variables to be loaded, causing the error:

     SyntaxError:
       (eval):1: unterminated string meets end of file
       (eval):1: syntax error, unexpected end-of-input, expecting '}'
       ...GE" => "Bump gem version 1.0.1

I've confirmed this isn't an issue for the build itself by creating a test PR. The build passes.

Please sign in to comment.