I don’t see why not here, given that it would go in to the master branch (which is our main development line). Clearly we wouldn’t want to auto release in such a state.
-Rob > On Jul 22, 2020, at 11:49 AM, Melloware <melloware...@gmail.com> wrote: > > Gary, > > I am a huge +1 on this feature for all those reasons. Nice work! > > Mello > > On 7/22/2020 11:34 AM, Gary Gregory wrote: >> Hi, >> >> There is no telling what any version change means to any library >> generically. We can only assume that some people follow semver and don't >> break BC. But there is no guarantee. IMO, it's better for Dependabot to >> make us aware of any change available. We also have the benefits of the PRs >> being built by GitHub which is nice. >> >> Gary >> >> On Wed, Jul 22, 2020 at 11:12 AM Xeno Amess <xenoam...@gmail.com> wrote: >> >>> as title. >>> I see some dependency trying to upgrade from v1 to v2.3.1, and some plugin >>> from 3.5.1 to 5.1.1 >>> Just confused. >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
