Managing GitHub-hosted components in 4D has become remarkably streamlined. To fully take advantage of it, it is important to understand how the latest tools work together and what makes each one stand out.

• Automatic Update (4D v20 R8+)

This feature allows 4D to periodically check your GitHub components for newer versions. If updates are available, you’ll see a visual indicator in the Components section (Project Dependencies). You stay in control—updates only happen when you explicitly approve them.

Use it when: you want to stay up to date with component improvements and bug fixes, but maintain manual control over when and how updates happen.


• Follow 4D Version Rule (4D v20 R9 beta)

The Follow 4D Version rule takes a different approach. Instead of tracking the latest release, it matches the component version to the version of 4D you are currently using.
To make this work, component authors must tag their GitHub releases using 4D’s versioning convention:



• LTS versions: x.y.p (e.g., 20.2.1)


• R-releases: xRy.p (e.g., 20R9.1)



When this rule is active, 4D will automatically resolve the correct component version based on your current 4D build, ensuring optimal compatibility without requiring manual selection.

Use it when: you want to ensure your component version always matches your 4D runtime environment—ideal for long-term maintenance and minimizing version mismatches.