Currently autopr will automatically create PRs for new patch and (depending on settings) minor releases. However, it would be useful to also automatically notify about opportunities and/or requirements to update to new major releases.
With unknown breaking changes possible, it would not be appropriate for autopr to submit a major-release PR, but it should be straightforward enough to open issues on a per-project basis.
These could take two different forms:
an issue notifying that a new major release series is available and requesting support (this should probably be opt-in per project, but might be on by default for libraries)
an issue notifying that major release series in use by a project is going to go out of support in the near future (this should probably be on by default for all projects).
This should help to ensure that everyone stays as up to date as possible and that major release updates reliably take place in advance of the end-of-life date.
Currently autopr will automatically create PRs for new patch and (depending on settings) minor releases. However, it would be useful to also automatically notify about opportunities and/or requirements to update to new major releases.
With unknown breaking changes possible, it would not be appropriate for autopr to submit a major-release PR, but it should be straightforward enough to open issues on a per-project basis.
These could take two different forms:
an issue notifying that a new major release series is available and requesting support (this should probably be opt-in per project, but might be on by default for libraries)
an issue notifying that major release series in use by a project is going to go out of support in the near future (this should probably be on by default for all projects).
This should help to ensure that everyone stays as up to date as possible and that major release updates reliably take place in advance of the end-of-life date.