Skip to content

Commit cf41fbb

Browse files
authored
Address merge modification feature (#4277)
1 parent f7db9e8 commit cf41fbb

File tree

1 file changed

+8
-13
lines changed

1 file changed

+8
-13
lines changed

docs/manage/software/update-software.md

Lines changed: 8 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ To update the firmware on your microcontroller, see [Over-the-air updates](/oper
2020

2121
## Test and update software
2222

23-
You can either use fragment tags for testing or manually overwrite the version of the module or package for a subset of machines.
24-
We strongly recommend that you test updates on a subset of machines before deploying it to all machines.
23+
You can either use fragment tags for testing or manually overwrite the version of the module or package or the configuration for a subset of machines.
24+
We strongly recommend that you test changes on a subset of machines before deploying it to all machines.
2525

2626
{{< tabs >}}
2727
{{< tab name="Version tags (recommended)" >}}
@@ -39,7 +39,7 @@ On your fragment's page, click on **Versions** in the menu bar and add a tag cal
3939
For each machine that uses the fragment, update its configuration.
4040
{{% /tablestep %}}
4141
{{% tablestep number=4 %}}
42-
**Edit the fragment** and change the version of your module or package in the development fragment.
42+
**Edit the fragment** and change the version of your module or package or the configuration in the development fragment.
4343
This will create a new version of the fragment.
4444

4545
For example:
@@ -87,20 +87,15 @@ Click **Save** in the upper right corner of the screen.
8787

8888
{{% /tablestep %}}
8989
{{% tablestep number=2 %}}
90-
**Test the new version of your module or package.**
90+
**Test your changes.**
9191
{{% /tablestep %}}
9292
{{% tablestep number=3 %}}
9393
**Update the fragment.**
9494

95-
When you are satisfied that your module or package works as expected, update your fragment.
95+
When you are satisfied that your changes work as expected, click the **...** menu on the resource you updated and click **Merge changes**.
96+
This will create a new version of your fragment.
9697

97-
For example:
98-
99-
````json {class="line-numbers linkable-line-numbers"}
100-
{
101-
"version": "0.0.7"
102-
}
103-
```
98+
Fragment tags remain unchanged.
10499

105100
All machines configured with your fragment will update when they next check for configuration updates.
106101

@@ -195,4 +190,4 @@ async def main():
195190

196191
if __name__ == '__main__':
197192
asyncio.run(main())
198-
````
193+
```

0 commit comments

Comments
 (0)