pry-send_tweet.rb 1.17.8 → 1.17.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1642112fb14155f08e24ec2ffffbee20cb03cd43109df45f3d349e35658b273c
-  data.tar.gz: b47efba93bc8ea5b34bc9b8a258a98dc8a3fc4ab91eaaf3450dce463c484ce92
+  metadata.gz: 66109e9acc15ec0c0bd6350603ed05d505231c6c1aeffa9983811e9088ab38bd
+  data.tar.gz: 5894b2f4d43f6ce8a61afa95c1004c95b77157828a2fc0df290088a9d13fad14
 SHA512:
-  metadata.gz: 021e1e8480b41b964662b6bd7113ed60f812058cbb87412ac6aa4d6d4c530319200e109ecac008b301d04b761e4950fabb97fba0a905e97e69cc4fcfb3ad6945
-  data.tar.gz: 99dec9816528094b967497e2aaf7af47404f13ad8eec2479afe1a1632fdb1cb1ab196ebfe22e2fb01f8da83a21e8db833471d6ab9e249e587fe03aa9b806baa6
+  metadata.gz: 8f41ab17dcc4afd898c8107e0a080be2bbdb6656d999a4a83a10c27b5f76864d128acc81481592ef878accc8c83f03d6743e556439a8208302c895d48dfb9e8e
+  data.tar.gz: e3fdf0b7d925c7cb93982bfbea18d610beda19428339c47c2cd5d695b70b95bc1e0a86e8b455fc451f14b45e7e9614d0931b58af11b6b04572a82d329b5a8dcd

data/lib/pry/send_tweet/commands/easter_eggs.rb

@@ -485,7 +485,9 @@ Pry.commands.instance_eval do
      %q|The original telescope is a pipe, but not a crack pipe, that came after the telescope| => 'https://www.youtube.com/watch?v=k9dMdbUAi0c',
      %q|Observing a jquery riddled with XSS issuesB on the frontend and Rails4-5 on the backend shows us the pains of legacy, and a team too focused on backend technology. You got owned from the front.| => 'https://www.youtube.com/watch?v=25DC6v8oPxo',
      %q[Rails and webpack are a bad match. Why? Because webpack leaves a manfiest file in public/packs/, which might expose admin paths and keys, etc. Is that 0day? Are all modern Rails applications vulnerable to this? I don't think Rails understands JavaScript, and should not be the ruby leaders for such tech.] => 'https://www.youtube.com/watch?v=pHIua_4T0sY',
-     %q[Rails and webpack are a bad match. Why? Because webpack leaves a manfiest file in public/packs/, which might expose admin paths and keys, etc. Is that 0day? Are all modern Rails applications vulnerable to this? I don't think Rails understands JavaScript, and should not be the ruby leaders for such tech.] => 'https://www.youtube.com/watch?v=pHIua_4T0sY'
+     %q[Rails and webpack are a bad match. Why? Because webpack leaves a manfiest file in public/packs/, which might expose admin paths and keys, etc. Is that 0day? Are all modern Rails applications vulnerable to this? I don't think Rails understands JavaScript, and should not be the ruby leaders for such tech.] => 'https://www.youtube.com/watch?v=pHIua_4T0sY',
+     %q|That's strange, how do General Assembly (https://generalassemb.ly) continue to benefit from my knowledge, even though i no longer work there? Stop stealing from me. And pay me, bitch, @chadwpry.| => 'https://www.youtube.com/watch?v=-LdYXYNtPJI',
+     %q|That's strange, how do General Assembly (https://generalassemb.ly) continue to benefit from my knowledge, even though i no longer work there? Stop stealing from me. And pay me, bitch, @chadwpry.| => 'https://www.youtube.com/watch?v=-LdYXYNtPJI'
     }
   command '🎧', '' do
     args = arg_string.split(' ')

data/lib/pry/send_tweet/version.rb

@@ -1,6 +1,6 @@
 class Pry
   module SendTweet
-    VERSION  = '1.17.8'
+    VERSION  = '1.17.9'
     CODENAME = 'Virtus'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pry-send_tweet.rb
 version: !ruby/object:Gem::Version
-  version: 1.17.8
+  version: 1.17.9
 platform: ruby
 authors:
 - Pry developers