{"action":"created","issue":{"url":"https://api.github.com/repos/jwt/ruby-jwt/issues/132","repository_url":"https://api.github.com/repos/jwt/ruby-jwt","labels_url":"https://api.github.com/repos/jwt/ruby-jwt/issues/132/labels{/name}","comments_url":"https://api.github.com/repos/jwt/ruby-jwt/issues/132/comments","events_url":"https://api.github.com/repos/jwt/ruby-jwt/issues/132/events","html_url":"https://github.com/jwt/ruby-jwt/issues/132","id":136270165,"number":132,"title":"Version 1.5.3 breaks 1.9.3 compatibility, but not documented as such","user":{"login":"BanzaiMan","id":25666,"avatar_url":"https://avatars.githubusercontent.com/u/25666?v=3","gravatar_id":"","url":"https://api.github.com/users/BanzaiMan","html_url":"https://github.com/BanzaiMan","followers_url":"https://api.github.com/users/BanzaiMan/followers","following_url":"https://api.github.com/users/BanzaiMan/following{/other_user}","gists_url":"https://api.github.com/users/BanzaiMan/gists{/gist_id}","starred_url":"https://api.github.com/users/BanzaiMan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BanzaiMan/subscriptions","organizations_url":"https://api.github.com/users/BanzaiMan/orgs","repos_url":"https://api.github.com/users/BanzaiMan/repos","events_url":"https://api.github.com/users/BanzaiMan/events{/privacy}","received_events_url":"https://api.github.com/users/BanzaiMan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-25T03:52:32Z","updated_at":"2016-02-25T09:03:26Z","closed_at":null,"body":"Yes, I know 1.9.3 has been EOL'd many months ago. It is OK if this is a carefully considered decision. But https://github.com/jwt/ruby-jwt/blob/v1.5.3/ruby-jwt.gemspec does not indicate it.\r\n\r\nIt should be either indicated as such, or reinstate 1.9.x support.\r\n\r\nUpon `require`, it fails:\r\n\r\n```sh-session\r\n$ pry\r\n[1] pry(main)> require 'jwt'\r\nSyntaxError: /Users/asari/.rvm/gems/ruby-1.9.3-p551/gems/jwt-1.5.3/lib/jwt/verify.rb:7: unknown type of %string\r\n      %i[verify_aud verify_expiration ...\r\n         ^\r\n/Users/asari/.rvm/gems/ruby-1.9.3-p551/gems/jwt-1.5.3/lib/jwt/verify.rb:7: syntax error, unexpected $end\r\n      %i[verify_aud verify_expiration ...\r\n         ^\r\nfrom /Users/asari/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:54:in `require'\r\n```\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/jwt/ruby-jwt/issues/comments/188676766","html_url":"https://github.com/jwt/ruby-jwt/issues/132#issuecomment-188676766","issue_url":"https://api.github.com/repos/jwt/ruby-jwt/issues/132","id":188676766,"user":{"login":"danleyden","id":703685,"avatar_url":"https://avatars.githubusercontent.com/u/703685?v=3","gravatar_id":"","url":"https://api.github.com/users/danleyden","html_url":"https://github.com/danleyden","followers_url":"https://api.github.com/users/danleyden/followers","following_url":"https://api.github.com/users/danleyden/following{/other_user}","gists_url":"https://api.github.com/users/danleyden/gists{/gist_id}","starred_url":"https://api.github.com/users/danleyden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danleyden/subscriptions","organizations_url":"https://api.github.com/users/danleyden/orgs","repos_url":"https://api.github.com/users/danleyden/repos","events_url":"https://api.github.com/users/danleyden/events{/privacy}","received_events_url":"https://api.github.com/users/danleyden/received_events","type":"User","site_admin":false},"created_at":"2016-02-25T09:03:26Z","updated_at":"2016-02-25T09:03:26Z","body":"I wonder if the bump to 1.5.3 from 1.5.2 should have been a major bump\n(breaking backwards-compatibility) per semantic versioning?\n\nOn 25 February 2016 at 03:52, Hiro Asari <notifications@github.com> wrote:\n\n> Yes, I know 1.9.3 has been EOL'd many months ago. It is OK if this is a\n> carefully considered decision. But\n> https://github.com/jwt/ruby-jwt/blob/v1.5.3/ruby-jwt.gemspec does not\n> indicate it.\n>\n> It should be either indicated as such, or reinstate 1.9.x support.\n>\n> Upon require, it fails:\n>\n> $ pry[1] pry(main)> require 'jwt'SyntaxError: /Users/asari/.rvm/gems/ruby-1.9.3-p551/gems/jwt-1.5.3/lib/jwt/verify.rb:7: unknown type of %string      %i[verify_aud verify_expiration ...         ^/Users/asari/.rvm/gems/ruby-1.9.3-p551/gems/jwt-1.5.3/lib/jwt/verify.rb:7: syntax error, unexpected $end      %i[verify_aud verify_expiration ...         ^from /Users/asari/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:54:in `require'\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/jwt/ruby-jwt/issues/132>.\n>\n"}}