docs: update documentation for automated package updates workflow

docs/CONTRIBUTING.md

@@ -110,6 +110,8 @@ in {
 
 See [Adding Packages Guide](./guides/adding-packages.md) for detailed instructions.
 
+**Note**: Package versions are automatically updated weekly via Gitea Actions using `nix-update`. You don't need to worry about keeping versions current - the automation will create PRs for updates. Just focus on ensuring the package builds and works correctly.
+
 ### Package Testing
 
 ```bash
@@ -270,6 +272,17 @@ nix flake show
 6. [ ] Documentation updated if needed
 7. [ ] Commit messages follow convention
 
+### Handling Automated Update PRs
+
+The repository has automated package updates via Gitea Actions (see main README for details). When reviewing automated update PRs:
+
+1. **Build and test**: Verify the updated package builds successfully
+2. **Check changelinks**: Review upstream release notes for breaking changes
+3. **Test functionality**: Ensure the package still works as expected
+4. **Review package definition**: Check if any manual adjustments are needed
+
+For urgent updates, you can manually trigger the workflow from the Gitea UI or update the package manually.
+
 ### PR Description
 
 Include:

docs/guides/adding-packages.md

@@ -18,6 +18,17 @@ nix flake init -t .#package my-new-package
 
 This creates a template structure in `templates/package/` that you can copy.
 
+### Automatic Updates
+
+**Important**: This repository uses automated package updates via Gitea Actions and `nix-update`. When adding a new package:
+
+- Use any stable, working version for the initial package
+- You don't need to use the absolute latest version
+- The automation will keep the package updated automatically on a weekly basis
+- Review and merge automated update PRs as they come in
+
+See the main README.md for more details on the automated update workflow.
+
 ### Manual Setup
 
 1. Create directory: `pkgs/your-package/`