Repository Activation¶
After publishing packages to the SynoCommunity repository, you need to activate them before they become available to users.
Prerequisites¶
- Maintainer access to the SynoCommunity repository
- Successfully built and uploaded packages (via GitHub Actions or manual publishing)
Activation Process¶
1. Check Your Builds¶
- Log in at synocommunity.com/admin/
- Navigate to synocommunity.com/admin/build/
- Find your recently uploaded builds
2. Test Activation¶
Before making packages publicly available:
- Activate your test build from the admin panel
- Install/upgrade from DSM Package Center to verify functionality
- Test core features work as expected
3. Version Activation¶
If testing is successful:
- Navigate to synocommunity.com/admin/version/
- Activate the Version to make it publicly available
- Users will see the update in Package Center
Package Signing¶
DSM Version Differences
- DSM 6.x: Package signing ensures that packages are recognized as coming from a trusted publisher. Users must configure their trust level settings to allow installation of packages signed by Synology Inc. and trusted publishers.
- DSM 7+: Only Synology-signed packages are trusted. All community packages will always show a third-party warning during installation, regardless of signing.
See Also¶
- GitHub Actions CI/CD - Automated builds and publishing
- Manual Publishing - Publishing without CI
- Update Policy - Supported versions and testing checklist