You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/upgrading.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,16 @@
4
4
5
5
If upgrades between versions require manual actions, those are described here.
6
6
7
-
# to v4.0.0
7
+
##to v4.0.0
8
8
9
9
For breaking changes to functionality, see the release notes. Upgrade as follows:
10
10
11
-
## Using the binary directly
11
+
###Using the binary directly
12
12
13
13
1. Upgrade to v3.22.2 before upgrading to v4.0.0.
14
14
2. Upgrade to v4.0.0
15
15
16
-
## Using the OCI image
16
+
###Using the OCI image
17
17
18
18
With the upgrade to v4.0.0, the image will now run rootless.
19
19
@@ -22,11 +22,11 @@ With the upgrade to v4.0.0, the image will now run rootless.
22
22
3. Update the ownership of the database file. Enter the directory where it is stored and run `chown 65532:65532 gorm.db` to update the permissions to the user the image is now using.
23
23
4. Upgrade to v4.0.0
24
24
25
-
# to v3.0.0
25
+
##to v3.0.0
26
26
27
27
v3.0.0 does not require manual steps. With v3.0.0, account names must be unique per budget.
28
28
29
-
# to v2.0.0
29
+
##to v2.0.0
30
30
31
31
v2.0.0 does not require manual steps. With v2.0.0, spent amounts are now negative values instead of positive values.
0 commit comments