The intent of this issue is to help the maintainer(s) coordinate community efforts in the creation of the next stable release. Community involvement is only intended as a suggestion; it is up to maintainers to ultimately decide the creation of, and what goes into, a stable release. If the maintainer(s) are not interested in using this issue, please mark the issue as Fixed or Closed (works as designed).
As of the creation of this issue, this project presently does not have a stable release compatible with Drupal 11+. There are many benefits to publishing a stable release for a module. Project Browser → uses stable releases as a recommended criteria for module discovery ( #3240314-16: Decide on algorithm for "recommended" modules → ).
Maintainers should enter tickets as [#123456] to take advantage of drupal.org issue linking and status highlighting.
This issue uses a proposed 'Stable Release Request' Issue Template. Do you have resources you'd like to contribute to this template? Have feedback on the stable release request issue template? We want your feedback: [ #3239062 → ].
Active
1.0
Code
Obviously, if any tickets make the list that introduce breaking changes, going with 2.0.0 is appropriate. However, given the broad community adoption of the un-prefixed, semantic version, it may be prudent to use this opportunity to make the switch now to 2.0.0, even if no breaking changes are introduced. Just something to consider.