midnight_ride 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 737728c4a69dcca4fce7ad8442c79e0d8203f3531e09d74a4196f5b7a11a6a77
4
- data.tar.gz: 06ecb0e71aeea5f6f3823b84de93561a330fae00e4a79c2fe8c034b6f53ff32a
3
+ metadata.gz: 0c0dd674a875e425f13ae5c28eafedee9e711cd702f0a401548e2b693fe56dd9
4
+ data.tar.gz: 812b1f08dadd8c84d4d59cdf913b2ac83eb6de3bc8e56ff2eee869a4f9f5153c
5
5
  SHA512:
6
- metadata.gz: 5fbedf3a0a64c1f26a2a3645248b0e4ced4177b3b1dd3ad05713e63d840fa6497399a070e9644e271547c1cce85bfcc40b37fd59038b3532ec1cebdb6a5f8142
7
- data.tar.gz: a339d43582e6d5fb128137af6411361fce88fac07e6350741a6c2484d00cfd7281bab663bc8092620cf4e1873bbd16f3ae841108e854f9ee8ecb84e45eb6be90
6
+ metadata.gz: a1eb43458158d3b43e41cd0139a8ee3d9b535b0a4aad20f341b3b9f2181d6d76a88cc695a71cc23bc382ab0aea05b1babd85085a7ba33b9fca98a4dc7a57b423
7
+ data.tar.gz: ed603984c06997547dfe5448b695fa47fbca2ffa2508105e8caa59ab6df83b003a675afd0c0dae23964c7fe10c56a10caf681f129b40a80e6285c4418248691d
data/README.md CHANGED
@@ -30,17 +30,20 @@ it’s sent. Even so, an error message can hold text an attacker chose, so
30
30
  keep a person between the session and production: review its pull requests
31
31
  before they’re merged.
32
32
 
33
- Protect the branch you deploy from on GitHub (Settings → Branches): require
34
- pull requests, and let no one bypass the rule. Otherwise a session could
35
- push straight to it, and if your server deploys that branch by itself, a
36
- tricked session could ship code without anyone reviewing it.
33
+ Reviewing only helps if a session can’t skip it. Claude Code sessions reach
34
+ GitHub as you, so branch protection can’t tell them apart from you: a
35
+ session tricked by an error message could push to the branch you deploy
36
+ from, or merge its own pull request. So don’t let anything a session can do
37
+ reach production by itself. Make deploys need something only you can
38
+ produce, such as a deploy you start yourself, or a tag signed with a key
39
+ that only you hold, which your server checks before deploying.
37
40
 
38
41
  ## Setup
39
42
 
40
43
  1. Add the gem, and Solid Errors if the app doesn’t have it yet:
41
44
 
42
45
  ```ruby
43
- gem "midnight_ride", github: "dchacke/midnight_ride"
46
+ gem "midnight_ride"
44
47
  ```
45
48
 
46
49
  2. Create a Telegram bot with [@BotFather](https://t.me/BotFather) and send
@@ -1,3 +1,3 @@
1
1
  module MidnightRide
2
- VERSION = "0.1.0"
2
+ VERSION = "0.1.1"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: midnight_ride
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Dennis Hackethal