Commit b9e6098
authored
bump viper incrementally (#168)
#159 attempts to bump `spf13/viper` from `1.19.0` to `1.20.1`, but there
is a failing GHA because the `e2e-tests` job gets the diff of the PR
from the GitHub API, and the diff is so huge that it exceeds the max
number of lines that can be returned from the GET pull request endpoint
(ripping out a bunch of unneeded code). So this PR bumps the version
incrementally to `1.20.0-alpha.1` which accounts for roughly half the
changes, and passes the `e2e-tests` job. We can then immediately upgrade
from `1.20.0-alpha.1` to `1.20.1` and I believe that diff should be
small enough as well. This means we'd be on an alpha version for a brief
time, which is a bit dicey, but I think acceptable. In any event, I'm
not sure how else we're going to get around this issue, unless we want
to dig into what the test is doing and try to come up with an acceptable
substitute, but that feels substantially riskier, actually. Thoughts?1 parent 9e31145 commit b9e6098
84 files changed
Lines changed: 2448 additions & 7045 deletions
File tree
- vendor
- github.com
- go-viper/mapstructure/v2
- internal/errors
- mitchellh/mapstructure
- sagikazarmark
- locafero
- slog-shim
- spf13/viper
- internal/features
- golang.org/x/exp
- constraints
- slices
- slog
- internal
- buffer
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
10 | | - | |
| 10 | + | |
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
25 | | - | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
26 | 28 | | |
27 | 29 | | |
28 | 30 | | |
29 | | - | |
| 31 | + | |
30 | 32 | | |
31 | 33 | | |
32 | 34 | | |
| |||
39 | 41 | | |
40 | 42 | | |
41 | 43 | | |
42 | | - | |
43 | 44 | | |
44 | 45 | | |
45 | 46 | | |
46 | 47 | | |
47 | 48 | | |
48 | | - | |
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | | - | |
53 | 52 | | |
54 | 53 | | |
55 | 54 | | |
| |||
68 | 67 | | |
69 | 68 | | |
70 | 69 | | |
71 | | - | |
72 | 70 | | |
73 | 71 | | |
74 | 72 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| 71 | + | |
| 72 | + | |
71 | 73 | | |
72 | 74 | | |
73 | 75 | | |
| |||
170 | 172 | | |
171 | 173 | | |
172 | 174 | | |
173 | | - | |
174 | | - | |
175 | 175 | | |
176 | 176 | | |
177 | 177 | | |
| |||
197 | 197 | | |
198 | 198 | | |
199 | 199 | | |
200 | | - | |
201 | | - | |
202 | | - | |
203 | | - | |
| 200 | + | |
| 201 | + | |
204 | 202 | | |
205 | 203 | | |
206 | 204 | | |
| |||
215 | 213 | | |
216 | 214 | | |
217 | 215 | | |
218 | | - | |
219 | | - | |
| 216 | + | |
| 217 | + | |
220 | 218 | | |
221 | 219 | | |
222 | 220 | | |
| |||
262 | 260 | | |
263 | 261 | | |
264 | 262 | | |
265 | | - | |
266 | | - | |
267 | 263 | | |
268 | 264 | | |
269 | 265 | | |
| |||
Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 23 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 8 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
File renamed without changes.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments