docs: add notes

Author: Turtlepaw

docs/pages/developers/package.mdx

@@ -2,23 +2,23 @@ import { LinkButton } from "@/components/Button";
 import { Github } from "lucide-react";
 import { Callout, Steps } from "nextra/components";
 
-# Clockwork.yml
+# Clockwork.yaml
 
-Clockwork.yml is a file that contains metadata about a package.
+`clockwork.yaml` is a file that contains metadata about your project.
 
 ## Example
 
-```yaml copy filename="clockwork.yml"
+```yaml copy filename="clockwork.yaml"
 name: my-package
 description: My awesome clockwork package
 version: 1.0.0 # github release tag
 # Watch Face Format version that's required for installing your package
 watchFaceFormatVersion: 2 # or unspecified for any version
 ```
 
-<Callout type="warning">
-  The clockwork package file must be named `clockwork.yml` (`clockwork.yaml`
-  will be ignored).
+<Callout type="info">
+  Starting with 1.1.6, Clockwork accepts both `clockwork.yml` and
+  `clockwork.yaml` as package files.
 </Callout>
 
 ## Fields
@@ -31,6 +31,11 @@ watchFaceFormatVersion: 2 # or unspecified for any version
 | `watchFaceFormatVersion` | The version of Watch Face Format required to use the package. If unspecified, any version is allowed. |
 | [`scripts`](#scripts)    | Scripts to run when the package is installed or updated.                                              |
 
+<Callout type="info">
+  Currently `watchFaceFormatVersion` only warns the user and doesn't prevent
+  installation of the package. This will change in the future.
+</Callout>
+
 ## Scripts
 
 | Field         | Description                                                                  |

docs/pages/developers/registry.mdx

@@ -39,6 +39,10 @@ If you meet all these requirements, feel free to create a pull request.
 
 _Even if you meet all the requirements, your pull request may be rejected, but you are still **encouraged to create a pull request** if you haven't already._
 
+##### Recommendations for maintaining a package
+
+- If you introduce breaking changes, you should document it and publish it as a major (e.g. 1.0.0 -> 2.0.0) release so Clockwork doesn't automatically update it.
+
 ### Adding your package to the registry
 
 <Steps>

docs/pages/guides/packages.mdx

@@ -50,6 +50,25 @@ Clockwork works best in combination with [XML Preprocessor](https://github.com/g
 
 In this example, we import the component from `packages`, where Clockwork stores all your downloaded packages, currently this is the only way to import components from packages, but that will change in the future. Visit XML Preprocessor's [documentation on `<Import/>`](https://github.com/gondwanasoft/xml-preprocessor?tab=readme-ov-file#import) to learn more.
 
+## Updating packages
+
+You can update all your packages to minor and patch versions by running:
+
+```shell
+clockwork update
+```
+
+If you want to update your packages to major, minor, and patch versions, run:
+
+```shell
+clockwork upgrade
+```
+
+<Callout type="warning">
+  Major versions of packages may have breaking changes. Check the package's
+  documentation or changelog if you encounter issues.
+</Callout>
+
 ## Packages in the registry
 
 <Manifest />