|
| 1 | +- commits: |
| 2 | + - subject: Update layers/meta-balena to c51eede325137c7f6b5f3e01f3b9f9a39ff10ed0 |
| 3 | + hash: 228bf21fca252c6c1adebc35552feec8f33487d4 |
| 4 | + body: Update layers/meta-balena |
| 5 | + footer: |
| 6 | + Changelog-entry: Update layers/meta-balena to c51eede325137c7f6b5f3e01f3b9f9a39ff10ed0 |
| 7 | + changelog-entry: Update layers/meta-balena to c51eede325137c7f6b5f3e01f3b9f9a39ff10ed0 |
| 8 | + author: balena-renovate[bot] |
| 9 | + nested: |
| 10 | + - commits: |
| 11 | + - subject: Update balena-supervisor to v16.12.7 |
| 12 | + hash: 0b8267253da82eb0b1f485046e52c570c1d5168a |
| 13 | + body: | |
| 14 | + Update balena-supervisor from 16.12.0 to 16.12.7 |
| 15 | + footer: |
| 16 | + Change-type: patch |
| 17 | + change-type: patch |
| 18 | + author: balena-renovate[bot] |
| 19 | + nested: |
| 20 | + - commits: |
| 21 | + - subject: Release locks when removing apps |
| 22 | + hash: 026dc0aed29ce7d66cfdd8616d80d1f5daf3ad46 |
| 23 | + body: > |
| 24 | + This prevents leftover locks that can prevent other |
| 25 | + operations from |
| 26 | + |
| 27 | + taking place. |
| 28 | + footer: |
| 29 | + Change-type: patch |
| 30 | + change-type: patch |
| 31 | + author: Felipe Lalanne |
| 32 | + nested: [] |
| 33 | + version: balena-supervisor-16.12.7 |
| 34 | + title: "" |
| 35 | + date: 2025-03-06T19:11:18.704Z |
| 36 | + - commits: |
| 37 | + - subject: Log non-API errors during state poll |
| 38 | + hash: 6d00be20930398699da1006176dac1e81b2dbbd6 |
| 39 | + body: > |
| 40 | + The supervisor was failing silently if an error happened |
| 41 | + while establishing the |
| 42 | + |
| 43 | + connection (e.g. requesting the socket). |
| 44 | + footer: |
| 45 | + Change-type: patch |
| 46 | + change-type: patch |
| 47 | + author: Felipe Lalanne |
| 48 | + nested: [] |
| 49 | + - subject: Fix target poll healthcheck |
| 50 | + hash: f8bdb1433508dcaeff12a78d746256041ba1c414 |
| 51 | + body: > |
| 52 | + The Target.lastFetch time compared when performing the |
| 53 | + healthcheck |
| 54 | + |
| 55 | + resets any time a poll is attempted no matter the |
| 56 | + outcome. This changes |
| 57 | + |
| 58 | + the behavior so the time is reset only on a successful |
| 59 | + poll |
| 60 | + footer: |
| 61 | + Change-type: patch |
| 62 | + change-type: patch |
| 63 | + author: Felipe Lalanne |
| 64 | + nested: [] |
| 65 | + version: balena-supervisor-16.12.6 |
| 66 | + title: "" |
| 67 | + date: 2025-03-04T14:25:06.565Z |
| 68 | + - commits: |
| 69 | + - subject: Decrease balenaCloud api request timeout from 15m to 59s |
| 70 | + hash: 49163e92a013250f72ca7231e11945b465c4dd45 |
| 71 | + body: > |
| 72 | + This was mistakenly increased due to confusion between |
| 73 | + the timeout for |
| 74 | + |
| 75 | + requests to the supervisor's api vs the timeout for |
| 76 | + requests from the |
| 77 | + |
| 78 | + supervisor to the balenaCloud api. This separates the |
| 79 | + two configs and |
| 80 | + |
| 81 | + documents the difference between the timeouts whilst |
| 82 | + also decreasing |
| 83 | + |
| 84 | + the timeout for balenaCloud api requests to the |
| 85 | + correct/expected value |
| 86 | + footer: |
| 87 | + Change-type: patch |
| 88 | + change-type: patch |
| 89 | + author: Pagan Gazzard |
| 90 | + nested: [] |
| 91 | + version: balena-supervisor-16.12.5 |
| 92 | + title: "" |
| 93 | + date: 2025-03-04T13:35:26.801Z |
| 94 | + - commits: |
| 95 | + - subject: Don't revert to regular pull if delta server 401 |
| 96 | + hash: 2dc9d275b15a0802264bcd49e2f0dddbbadd2225 |
| 97 | + body: > |
| 98 | + If the Supervisor receives a 401 Unauthorized from the |
| 99 | + delta server |
| 100 | + |
| 101 | + when requesting a delta image location, we should |
| 102 | + surface the error |
| 103 | + |
| 104 | + instead of falling back to a regular pull immediately, |
| 105 | + as there could |
| 106 | + |
| 107 | + be an issue with the delta auth token, which refreshes |
| 108 | + after |
| 109 | + |
| 110 | + DELTA_TOKEN_TIMEOUT (10min), or some other edge case. |
| 111 | + footer: |
| 112 | + Change-type: patch |
| 113 | + change-type: patch |
| 114 | + Signed-off-by: Christina Ying Wang <christina@balena.io> |
| 115 | + signed-off-by: Christina Ying Wang <christina@balena.io> |
| 116 | + author: Christina Ying Wang |
| 117 | + nested: [] |
| 118 | + version: balena-supervisor-16.12.4 |
| 119 | + title: "" |
| 120 | + date: 2025-03-03T13:42:18.045Z |
| 121 | + - commits: |
| 122 | + - subject: Retry DELTA_APPLY_RETRY_COUNT (3) times during delta apply fail before |
| 123 | + reverting to regular pull |
| 124 | + hash: 341111f1f94cd9f17fd7be9b6f21e3bc22c9ad3a |
| 125 | + body: > |
| 126 | + This prevents an image download error loop where the |
| 127 | + delta image on the delta server is present, |
| 128 | + |
| 129 | + but some aspect of the delta image or the base image on |
| 130 | + the device does not match up, causing |
| 131 | + |
| 132 | + the delta to fail to be applied to the base image. |
| 133 | + |
| 134 | + |
| 135 | + Delta apply errors don't raise status codes as they are |
| 136 | + thrown from the Engine (although they should), |
| 137 | + |
| 138 | + so if an error with a status code is raised during this |
| 139 | + time, throw an error to the handler |
| 140 | + |
| 141 | + indicating that the delta should be retried until |
| 142 | + success. Errors with status codes raised during |
| 143 | + |
| 144 | + this time are largely network related, so falling back |
| 145 | + to a regular pull won't improve anything. |
| 146 | + |
| 147 | + |
| 148 | + Upon delta apply errors exceeding |
| 149 | + DELTA_APPLY_RETRY_COUNT, revert to a regular pull. |
| 150 | + footer: |
| 151 | + Change-type: patch |
| 152 | + change-type: patch |
| 153 | + Signed-off-by: Christina Ying Wang <christina@balena.io> |
| 154 | + signed-off-by: Christina Ying Wang <christina@balena.io> |
| 155 | + author: Christina Ying Wang |
| 156 | + nested: [] |
| 157 | + - subject: Revert to regular pull immediately on delta server failure (code 400s) |
| 158 | + hash: 1fc242200f78e4219aafc5bb91de8cf0916236af |
| 159 | + body: > |
| 160 | + If the delta server responds immediately with HTTP 4xx |
| 161 | + upon requesting a delta image, |
| 162 | + |
| 163 | + this means the server is not able to supply the |
| 164 | + resource, so fall back to a regular pull |
| 165 | + |
| 166 | + immediately. |
| 167 | + footer: |
| 168 | + Change-type: patch |
| 169 | + change-type: patch |
| 170 | + Signed-off-by: Christina Ying Wang <christina@balena.io> |
| 171 | + signed-off-by: Christina Ying Wang <christina@balena.io> |
| 172 | + author: Christina Ying Wang |
| 173 | + nested: [] |
| 174 | + version: balena-supervisor-16.12.3 |
| 175 | + title: "" |
| 176 | + date: 2025-02-19T20:51:53.085Z |
| 177 | + - commits: |
| 178 | + - subject: Update balena-io/deploy-to-balena-action action to v2.0.92 |
| 179 | + hash: c57622e2264e41078e907d6ba8de9d5206bb6293 |
| 180 | + body: > |
| 181 | + Update balena-io/deploy-to-balena-action from 2.0.74 to |
| 182 | + 2.0.92 |
| 183 | + footer: |
| 184 | + Change-type: patch |
| 185 | + change-type: patch |
| 186 | + author: balena-renovate[bot] |
| 187 | + nested: [] |
| 188 | + version: balena-supervisor-16.12.2 |
| 189 | + title: "" |
| 190 | + date: 2025-02-11T01:04:22.736Z |
| 191 | + - commits: |
| 192 | + - subject: Pin io-ts version to v2.2.20 |
| 193 | + hash: 88e821ed8e36e10d6429dc31950b5aeed968aa3f |
| 194 | + body: > |
| 195 | + gcanti/io-ts#705 fixes an issue with io-ts and |
| 196 | + non-enumerable |
| 197 | + |
| 198 | + properties, but that results in objects with invalid |
| 199 | + properties to get |
| 200 | + |
| 201 | + removed during `decode`, which breaks our validation |
| 202 | + tests. |
| 203 | + |
| 204 | + |
| 205 | + Need to figure out what is the right behavior for us |
| 206 | + footer: |
| 207 | + Change-type: patch |
| 208 | + change-type: patch |
| 209 | + author: Felipe Lalanne |
| 210 | + nested: [] |
| 211 | + - subject: Update network-manager to v1 |
| 212 | + hash: f71f98777cbf7198745f1dcb8467b8cc62719d85 |
| 213 | + body: "" |
| 214 | + footer: |
| 215 | + Change-type: patch |
| 216 | + change-type: patch |
| 217 | + author: Felipe Lalanne |
| 218 | + nested: [] |
| 219 | + - subject: Update balena-request and balena-register-device |
| 220 | + hash: 52081ba15e84be794a906d5cbccc343b24748bba |
| 221 | + body: "" |
| 222 | + footer: |
| 223 | + Change-type: patch |
| 224 | + change-type: patch |
| 225 | + author: Felipe Lalanne |
| 226 | + nested: [] |
| 227 | + - subject: Update pinejs-client-request to v8 |
| 228 | + hash: 342a2d4dac737274ab13a8b05eac0f1f036a5075 |
| 229 | + body: "" |
| 230 | + footer: |
| 231 | + Change-type: patch |
| 232 | + change-type: patch |
| 233 | + author: Felipe Lalanne |
| 234 | + nested: [] |
| 235 | + - subject: Update chai utility modules |
| 236 | + hash: 3a3889546d8546793914bc2b5da10e202ebb14b1 |
| 237 | + body: > |
| 238 | + Updating chai will be done in a future PR as it requires |
| 239 | + overhauling all |
| 240 | + |
| 241 | + tests since chai is now ESM |
| 242 | + footer: |
| 243 | + Change-type: patch |
| 244 | + change-type: patch |
| 245 | + author: Felipe Lalanne |
| 246 | + nested: [] |
| 247 | + version: balena-supervisor-16.12.1 |
| 248 | + title: "" |
| 249 | + date: 2025-02-10T22:51:51.632Z |
| 250 | + version: meta-balena-6.4.2 |
| 251 | + title: "" |
| 252 | + date: 2025-03-07T05:37:46.183Z |
| 253 | + version: 6.4.2 |
| 254 | + title: "" |
| 255 | + date: 2025-03-07T06:49:07.715Z |
1 | 256 | - commits:
|
2 | 257 | - subject: Update balena-yocto-scripts to 2dac8b83fc45756b7ff1327c71b15930281ba2c5
|
3 | 258 | hash: 778b52bc6d98e810d8bf04eac60266953b9285f8
|
|
0 commit comments