<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "bug" label: - https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Abug and verify the issue you're about to submit isn't a duplicate. ---> ### Checklist <!-- Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version. --> - [x] I'm using the latest version of the extension (Run `glab --version`) v1.87.0 - Extension version: _Put your extension version here_ - [x] Operating system and version: registry.gitlab.com/gitlab-org/cli:1.87.0 - [x] 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 <!-- on POSIX system (Linux, MacOS), run bash -c 'printf -- "- OS: %s\n- SHELL: %s\n- TERM: %s\n- GLAB: %s" "$(uname -srm)" "$SHELL" "$TERM" "$(glab --version)"' and replace the following section with the result. If you use non-POSIX system, fill in the section manually: - OS: Your operating system including version and architecture (Windows 11 - AMD64, MacOS Sonoma - ARM64) - SHELL: Your shell (bash, fish, zsh, ...) - TERM: Your terminal emulator (Kitty, Xterm2..) - GLAB: result of running `glab --version` (glab version 1.32.0 (2023-08-18)) --> - OS: - SHELL: - TERM: - GLAB: <!-- Please include any other information that you believe might be relevant in debugging. For example, you may include a shell framework like oh-my-zsh or other customizations like editing the prompt (PS1, PS2, and others). --> 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 <!--- Paste the activity log from your command line --> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem -->