Problem/Motivation

#3433699: Automated Drupal 11 compatibility fixes for openapi_rest

Proposed resolution

  • Hoping for a tag release as 8.x-2.0-rc4 or 8.x-2.0/2.0.0
  • Maybe a new branch 2.1.x and a 2.1.0-alpha1 tag release can ease and pave the way for a smoother update process
  • Allso. Not sure if the 2.1.x can work well with 8.x-2.x, so maybe a 3.0.x branch could help too with a 3.0.0-alpha1 release

Remaining tasks

User interface changes

API changes

Data model changes

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Status: Active » Needs review
rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Priority: Normal » Major
rajab natshah’s picture

Hoping for a tag release to work with Drupal 11.2.0

rajab natshah’s picture

Priority: Major » Critical
rajab natshah’s picture

rajab natshah’s picture

rajab natshah’s picture

Hoping for a tag release.

rajab natshah’s picture

Category: Support request » Plan
richgerdes’s picture

Status: Needs review » Active

@rajab natshah, thanks for putting this together.

I don't think we can mix 8.x-2.x and 2.1.x branches. We can just stick with the 2.x versioning. I think given there have been no functional changes and only changes to fix a small typo and test functionality, I think its safe to just declare a 2.0 release from the latest 8.x-2.x.

richgerdes’s picture

Status: Active » Fixed

I've tagged and created the 8.x-2.0 release.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

rajab natshah’s picture

Thank you, Rich.
That’s so nice.
You’re right about the 8.x-2.x branch - you have better plans for this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.