When druid core is updated what is the best way to push releases to all druids without manually updating the packages in each and every project?
The current manual process is to update the druid core package version using search and replace in vs code. This is an all or nothing scenario. When anything changes in druid core ALL package are updated to the same version. After the packages are built for prod using the bin script (bin/build_libs_prod.sh) then released using the release bin script (bin/publish_libs.sh). Once released manually update the package version of all druid packages in each druid to the most recent release. This is done by a search and replace of the package.json file for druid.
Considerations
Auto updates to druids and extensions. If a druid updates core without updating the extension things will break. Extensions require an exact version match on shared package including druid core.
Improvements
Continuous deployment for core packages using github actions.
Automatically update version in each core package.
When druid core is updated what is the best way to push releases to all druids without manually updating the packages in each and every project?
The current manual process is to update the druid core package version using search and replace in vs code. This is an all or nothing scenario. When anything changes in druid core ALL package are updated to the same version. After the packages are built for prod using the bin script (bin/build_libs_prod.sh) then released using the release bin script (bin/publish_libs.sh). Once released manually update the package version of all druid packages in each druid to the most recent release. This is done by a search and replace of the package.json file for druid.
Considerations
Auto updates to druids and extensions. If a druid updates core without updating the extension things will break. Extensions require an exact version match on shared package including druid core.
Improvements