glab release create requires -notes even on update

Checklist

• I'm using the latest version of the extension (Run glab --version) v1.87.0
  • Extension version: Put your extension version here
• Operating system and version: registry.gitlab.com/gitlab-org/cli:1.87.0
• Gitlab.com or self-managed instance? gitlab.com
• GitLab version (if self-managed) GitLab version here (Use the version endpoint, like this: gitlab.my-company.com/api/v4/version)
• I have performed glab auth status to check for authentication issues
• Run the command in debug mode (like DEBUG=true glab mr list) and attach any useful output

Summary

When using glab release create to update update an existing release it asks for -notes. I can see why it's required when creating, but not when updating.

Environment

• OS:
• SHELL:
• TERM:
• GLAB:

Other:

Steps to reproduce

Just do glab release create on an existing release to update the --release-at field

What is the current bug behavior?

It's asking for --notes

What is the expected correct behavior?

It should succeed, the release already has notes

Relevant logs and/or screenshots

Possible fixes