Commit 92fcd2f
committed
Skip redirect sources that already exist when cutting a release
The nav patch step in cut-release adds a dated sibling redirect for
every /specification/draft/... entry, but it never checked whether that
dated source was already present. When main already carries the
<version>/ redirects, the loop appends a second copy of each source and
Mintlify rejects the resulting docs.json for reusing a source path,
which is exactly what broke the 2026-07-28 release PR. Track the
existing sources in a set and skip any collision so the step is
idempotent regardless of what main already contains.
:house: Remote-Dev: homespace1 parent bbcfe53 commit 92fcd2f
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
164 | 164 | | |
165 | 165 | | |
166 | 166 | | |
| 167 | + | |
| 168 | + | |
167 | 169 | | |
168 | 170 | | |
169 | 171 | | |
| 172 | + | |
170 | 173 | | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
171 | 177 | | |
172 | 178 | | |
173 | | - | |
| 179 | + | |
174 | 180 | | |
175 | 181 | | |
176 | 182 | | |
| |||
0 commit comments