This commit is contained in:
flowzone-app[bot] 2024-07-03 03:06:16 +00:00 committed by GitHub
parent e2ad3cb65d
commit b6595761b8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 137 additions and 1 deletions

View file

@ -1,3 +1,108 @@
- commits:
- subject: Update layers/meta-balena to e6c2037615db74af70250c5d3351c44e2ee31fbb
hash: 450aa1d8ab1ed919d5458e4cdc0a9fc7e619f0af
body: Update layers/meta-balena
footer:
Changelog-entry: Update layers/meta-balena to e6c2037615db74af70250c5d3351c44e2ee31fbb
changelog-entry: Update layers/meta-balena to e6c2037615db74af70250c5d3351c44e2ee31fbb
author: Self-hosted Renovate Bot
nested:
- commits:
- subject: Update balena-supervisor to v16.3.17
hash: 521d51db1023846cf95e40a9f2b0a514ec8aea6d
body: |
Update balena-supervisor from 16.3.15 to 16.3.17
footer:
Change-type: patch
change-type: patch
author: Self-hosted Renovate Bot
nested:
- commits:
- subject: Fix engine deadlock on network+service change
hash: ede27b63cecc2a9ae3139a905d9c6ab32418a72b
body: >
This fixes a regression on the supervisor state engine
computation
(added on v16.2.0) when
the target state removes a network at the same time that
a service
referencing that network is changed. Example going from
```
services:
one:
image: alpine: 3.18
networks: ['balena']
networks:
balena:
```
to
```
services:
one:
image: alpine: latest
```
Would never reach the target state as killing the
service in order to
remove the network is prioritized, but one of the
invariants in the target state calculation is
to not kill any services until all images have been
downloaded. These
two instructions were in contradiction leading to a
deadlock.
The fix involves only adding removal steps for services
depending on a
changing network or volume if the service container is
not being removed
already.
footer:
Change-type: patch
change-type: patch
author: Felipe Lalanne
nested: []
version: balena-supervisor-16.3.17
title: ""
date: 2024-06-25T01:03:26.734Z
- commits:
- subject: Update balena-io/deploy-to-balena-action action to v2.0.72
hash: 170733422a7a8fb2e58482508fe74dc2fcb282a5
body: >
Update balena-io/deploy-to-balena-action from 2.0.71 to
2.0.72
footer:
Change-type: patch
change-type: patch
author: Self-hosted Renovate Bot
nested: []
version: balena-supervisor-16.3.16
title: ""
date: 2024-06-17T01:56:08.257Z
version: meta-balena-5.3.23
title: ""
date: 2024-07-02T14:03:58.762Z
version: 5.3.23
title: ""
date: 2024-07-03T03:06:10.539Z
- commits:
- subject: Update balena-yocto-scripts to da6fe23e89509549866b16cbc6ff404980a189c0
hash: 01713ba300bfca5d9a34fb1fbcdd8c333a73b098

View file

@ -1,6 +1,37 @@
Change log
-----------
# v5.3.23
## (2024-07-03)
<details>
<summary> Update layers/meta-balena to e6c2037615db74af70250c5d3351c44e2ee31fbb [Self-hosted Renovate Bot] </summary>
> ## meta-balena-5.3.23
> ### (2024-07-02)
>
>
> <details>
> <summary> Update balena-supervisor to v16.3.17 [Self-hosted Renovate Bot] </summary>
>
>> ### balena-supervisor-16.3.17
>> #### (2024-06-25)
>>
>> * Fix engine deadlock on network+service change [Felipe Lalanne]
>>
>> ### balena-supervisor-16.3.16
>> #### (2024-06-17)
>>
>> * Update balena-io/deploy-to-balena-action action to v2.0.72 [Self-hosted Renovate Bot]
>>
>
> </details>
>
>
</details>
# v5.3.22+rev2
## (2024-07-03)

View file

@ -1 +1 @@
5.3.22+rev2
5.3.23