pry-send_tweet.rb 1.17.7 → 1.17.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0cf3492f9e96a8d8743c77485b52154f1d0a3ccc99b9ee920e22718417cc16f4
-  data.tar.gz: 1ad3730a08579c0592e8e5ac3214d91fc520ccf056cbd07316281dd964871a82
+  metadata.gz: 1642112fb14155f08e24ec2ffffbee20cb03cd43109df45f3d349e35658b273c
+  data.tar.gz: b47efba93bc8ea5b34bc9b8a258a98dc8a3fc4ab91eaaf3450dce463c484ce92
 SHA512:
-  metadata.gz: fec48178b56434644a638b9519a873f2ee913c84a56433885bedbdd241b4777d08f32b17480686ea2f984c023a7ddae67c51893a1e327aa7511109b4e76cb5ea
-  data.tar.gz: e3d5c06fd0dd1a4684cc4773381d8a21758a3164c280454826eaabd1aeaffd6c2eaf8c9d886637ef7c4ae31a27030b4ce849a4c0250268543f0f15c48b8ad33d
+  metadata.gz: 021e1e8480b41b964662b6bd7113ed60f812058cbb87412ac6aa4d6d4c530319200e109ecac008b301d04b761e4950fabb97fba0a905e97e69cc4fcfb3ad6945
+  data.tar.gz: 99dec9816528094b967497e2aaf7af47404f13ad8eec2479afe1a1632fdb1cb1ab196ebfe22e2fb01f8da83a21e8db833471d6ab9e249e587fe03aa9b806baa6

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # CHANGELOG
 
+## v1.17.8
+
+* Add warning(s)
+
 ## v1.17.7
 
 * Add art

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

@@ -484,6 +484,7 @@ Pry.commands.instance_eval do
      %q|Why did the Dutch break rank, the Irish deserve no better than Soap Bar, they're far from clean| => 'https://www.youtube.com/watch?v=0EioRyzcvJo',
      %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'
     }
   command '🎧', '' do

data/lib/pry/send_tweet/version.rb

@@ -1,6 +1,6 @@
 class Pry
   module SendTweet
-    VERSION  = '1.17.7'
+    VERSION  = '1.17.8'
     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.7
+  version: 1.17.8
 platform: ruby
 authors:
 - Pry developers