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/digging-deeper/updating-hyde.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,24 @@ This guide will help you update your HydePHP project to the latest version.
13
13
When updating an existing installation, first ensure that you have a backup of your project in case anything goes wrong.
14
14
The recommended way to do this is to use Git as that allows you to smoothly roll back any changes.
15
15
16
+
## Version compatibility
17
+
18
+
HydePHP follows [semantic versioning](https://semver.org/), so you can expect that minor and patch releases will be backwards compatible.
19
+
Only major releases may introduce breaking changes, all of which are thoroughly documented in the accompanying release notes.
20
+
21
+
New features and bug fixes are added in minor and patch releases, so it is recommended to keep your project up to date.
22
+
23
+
### Side effects and ensuring a smooth update
24
+
25
+
Please note that due to the intricate nature of software, there is a possibility that an update contains side effects,
26
+
hence why version controlling your site is helpful when updating versions as you can roll back changes. It can also
27
+
be helpful to version control the compiled HTML, so you can view a diff of the changes. Be sure to test that your site
28
+
can be built and that it looks as expected after updating before deploying the changes to your live site.
29
+
30
+
We of course have extensive tests in place run on each single code commit to ensure all code is functional, however,
31
+
it is still possible that some edge cases slip through. This means that a bug fix may impact an edge case that you depend on.
32
+
33
+
Obligatory related XKCD: [https://xkcd.com/1172](https://xkcd.com/1172)
16
34
17
35
## Methods
18
36
@@ -25,6 +43,17 @@ update your project. If you are not using Git, you can still update your project
25
43
26
44
Regardless of the method you use, make sure you follow the [post-update instructions](#post-update-instructions) at the end.
27
45
46
+
### Updating just the Framework
47
+
48
+
If you just want to update the framework patch version, you can do so by running the following command:
49
+
50
+
```bash
51
+
composer update hyde/framework
52
+
```
53
+
54
+
While the same can still be done for minor versions, it's best to also update your project scaffolding and resources to
55
+
ensure that everything is up to date, for which you should use the methods below.
56
+
28
57
### Using Git
29
58
30
59
First, make sure you have a remote set up for the base project repository.
@@ -117,3 +146,5 @@ Finally, you can rebuild your site.
117
146
```bash
118
147
php hyde build
119
148
```
149
+
150
+
Now, you should browse your site files to ensure things are still looking as expected.
0 commit comments