Repository navigation
Commit 48f320d
committed
publish: record the https clone URL in the StepLib, not the SSH one
`bitrise share create --git <url>` writes its argument into the published
step.yml as `source.git`, and that is the URL every user's Bitrise CLI clones
the Step from, anonymously. publish.sh passed the same git@github.com: URL it
uses to push, so the first release would have shipped a Step nobody outside
the org could run -- and a published version is immutable, so the only remedy
would have been to publish another one.
Pushing still uses SSH; only the recorded URL changes. Every entry in the
StepLib is https, including this Step's own 0.0.1, which is what the dry run
was checked against.1 parent 8cfa1d8 commit 48f320d
1 file changed
Lines changed: 11 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
68 | 76 | | |
69 | 77 | | |
70 | 78 | | |
| |||
90 | 98 | | |
91 | 99 | | |
92 | 100 | | |
| 101 | + | |
93 | 102 | | |
94 | 103 | | |
95 | 104 | | |
| |||
105 | 114 | | |
106 | 115 | | |
107 | 116 | | |
108 | | - | |
| 117 | + | |
109 | 118 | | |
110 | 119 | | |
111 | 120 | | |
| |||
140 | 149 | | |
141 | 150 | | |
142 | 151 | | |
143 | | - | |
| 152 | + | |
144 | 153 | | |
145 | 154 | | |
146 | 155 | | |
| |||
0 commit comments