{"push_id":1341485723,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"463ae69c38a1c8c6070b487e4c4869dff571e06d","before":"34f76d9e0e585b20de83b2f46f7c1337d8b5e748","commits":[{"sha":"463ae69c38a1c8c6070b487e4c4869dff571e06d","author":{"name":"Chris Tessmer","email":"f7d2da5c71c6ca4d0a58de762f9daa072d59960f@onyxpoint.com"},"message":"(SIMP-1595) Provide complete dependency boundaries\n\nBefore this patch, dependencies in `metadata.json` and\n`build/rpm_metadata/requires` were missing upper boundaries and often\nlisted inaccurate lower boundaries.  This created an extremely fragile\n5.2.X/4.3.X module ecosystem on the Forge, as a major release in any\ndependency would be certain to break the module.\n\nThis commit resolves the issue by introducing upper and lower boundaries\nfor each dependency in `metadata.json` and propagates those dependencies\nto the RPM dependencies listed in `build/rpm_metadata/requires`.\n\nThe minimum version boundaries were determined from the modules as they\nwere checked out in `simp-core` for the latest SIMP 5.2.X/4.3.X release\n(with the addition recent z-version bumps from Forge-readiness patches).\n\nSIMP-1595 #comment Fixed `pupmod-simp-ntpd`\nSIMP-1608 #close\n\nChange-Id: Iac27cdf457e2a5f6dc94dfec29578f2738abb460","distinct":true,"url":"https://api.github.com/repos/simp/pupmod-simp-ntpd/commits/463ae69c38a1c8c6070b487e4c4869dff571e06d"}]}
{"actor":{"display_login":"simp-auto"}}