gh release create has some flags.
We want to support them.

FLAGS
      --discussion-category string   Start a discussion of the specified category
  -d, --draft                        Save the release as a draft instead of publishing it
  -n, --notes string                 Release notes
  -F, --notes-file file              Read release notes from file
  -p, --prerelease                   Mark the release as a prerelease
      --target branch                Target branch or full commit SHA (default: main branch)
  -t, --title string                 Release title

• --discussion-category
• --draft
• --notes
• --notes-file
• --prerelease
• --target
• --title

Tags:

Error: failed to run gh. err: exit status 1, eout: release not found

Usage:
  bump [flags]

Flags:
      --bump-type string             Bump type (major, minor or patch)
      --discussion-category string   Start a discussion of the specified category
  -d, --draft                        Save the release as a draft instead of publishing it
  -g, --generate-notes               Automatically generate title and notes for the release
  -h, --help                         help for bump
  -n, --notes string                 Release notes
  -F, --notes-file string            Read release notes from file
  -p, --prerelease                   Mark the release as a prerelease
  -R, --repo string                  Select another repository using the [HOST/]OWNER/REPO format
      --target string                Target branch or full commit SHA (default: main branch)
  -t, --title string                 Release title
  -y, --yes                          Answer 'yes' to all questions

exit status 1

I think result of gh release view was changed.

gh bump does not work on a repo tied to GHE when you are inside that directory. Is there a way to have gh bump figure out which GH_HOST to use like other gh commands in the cli?

Current workaround is to set the GH_HOST=ghe.company.com gh bump

Token storage change in latest release of gh

This is a message from the GitHub CLI team, maintainers of gh, writing to inform you that the most recent release of gh contains changes which may affect your extension. The latest release introduces the feature of storing authentication tokens in the system keyring (encrypted storage) instead of in a plain text file.
The keyrings that are supported are:

• Keychain on macOS

• GNOME Keyring on Linux (Secret Service dbus interface)

• Wincred on Windows

This has huge security benefits for the users of our tool and was one of our oldest outstanding issues. Unfortunately this change has the potential to break extensions that rely on utilizing the users authentication token to work.

In order to have continued compatibility with gh there are some actions you, as an extension author, need to take. These actions will depend on the implementation of your extension.

Extensions built in Go using go-gh:

1. Upgrade your go-gh version to v1.2.1, the latest version.

   • This can be done using go get github.com/cli/[email protected]

2. Verify that in your extension retrieval of the user authentication token is done using the auth.TokenForHost function.

   • If you were previously accessing the authentication token using any other method it will no longer work.
   • Automatic resolution of the authentication token when using the API clients will continue to work without changes.

All other extensions:

1. Verify that in your extension retrieval of the user authentication token is done by shelling out to the gh auth token command.

   • If you were previously accessing the authentication token using the gh config get command, reading the configuration file directly, or any other methods it will no longer work.

As of right now storing the authentication token in the system keyring is an opt-in feature, but in the near future it will be required and at that point if the changes above are not made then your extension will be broken for all users. If you have any questions/concerns about this change please feel free to open a discussion in the gh repo.

Thanks,
The GitHub CLI Team

Adding some tests for

• isInitial case
• release not found case
• newVersion method

https://app.codecov.io/gh/johnmanjiro13/gh-bump/blob/main/bumper.go

I will support bump-type option which accepts either one of patch, minor or major.
It allows run gh bump without running promptui.

gh-bump uses safeexec to run gh cli.
go-gh wraps gh binary execution.

Hi @johnmanjiro13 👋🏻

First, thanks for your extension, it is really useful for me on a daily basis.

One thing I am wondering is if it could also support assets upload to the release.

I know that this is a built-in feature of the GH cli but we face some kind of issue where

• We use gh-bump to create the new Tag + Release
• We use gh to upload the assets

But in the time between, a GitHub workflow has been triggered by the Tag pushed and fails since the assets are not there yet 😅

Have you some tips for us in that regard?

Many thanks 🙏🏻

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update goreleaser/goreleaser-action action to v6

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository