feat(release): prompt to create github release when no file changes

[fahslaj]

Current Behavior

Nx Release exits with a warning when changelog files and github releases are enabled and there are no changelog file changes. This means that there is no way to update a remote github release if the local changelog file is already up to date.

Expected Behavior

When changelog files and github releases are enabled and there are no changelog file changes, the end user is prompted to see if they want to create a github release anyway. This allows users to update a remote github release regardless of the state of a local changelog file, like in the case where the remote release was updated in the github UI.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Feb 21, 2024 4:14pm

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit fef5b07961dede3ba7b80c8340af37c8831bbc45. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=cfa081538556738b8e9d4c75d39df6d597f1d360 --head=fef5b07961dede3ba7b80c8340af37c8831bbc45 --parallel=1
• nx affected --targets=lint,test,build --base=cfa081538556738b8e9d4c75d39df6d597f1d360 --head=fef5b07961dede3ba7b80c8340af37c8831bbc45 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=cfa081538556738b8e9d4c75d39df6d597f1d360 --head=fef5b07961dede3ba7b80c8340af37c8831bbc45
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=cfa081538556738b8e9d4c75d39df6d597f1d360 --head=fef5b07961dede3ba7b80c8340af37c8831bbc45

---

Sent with 💌 from NxCloud.

[github-actions[bot]]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.