You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default in unauthenticated mode, changelogen will open a browser link to make manual release. By providing github token, it can be automated.
Using GitHub CLI token when authenticated with gh auth login
Locally:
❯ gh auth status
github.com
✓ Logged in to github.com account danielpza (keyring)
❯ npm run release
> changelogen-gh-cli-issue@0.0.0 release
> changelogen --release --push
ℹ Generating changelog for ...master 6:09:56 PM
ℹ Bumping npm package version from 0.0.0 to 0.0.1 (patch) 6:09:56 PM
ℹ Creating /home/daniel/projects/changelog-gh-cli-issue/CHANGELOG.md 6:09:56 PM
ℹ Followup in the browser to manually create the release. 6:09:58 PM
However when feeding the GH token manually it does work as expected:
❯ GH_TOKEN=$(gh auth token) npm run release
> changelogen-gh-cli-issue@0.0.1 release
> changelogen --release --push
ℹ Generating changelog for v0.0.1...v0.0.1 6:11:08 PM
ℹ Bumping npm package version from 0.0.1 to 0.0.2 (patch) 6:11:08 PM
ℹ Updating /home/daniel/projects/changelog-gh-cli-issue/CHANGELOG.md 6:11:08 PM
✔ Synced v0.0.2 to Github releases! 6:11:10 PM
Additional context
No response
Logs
No response
The content you are editing has changed. Please copy your edits and refresh the page.
Environment
package and node version
OS: linux
Reproduction
https://github.com/danielpza/changelog-gh-cli-issue
Describe the bug
changelogen doesn't pick the authentication from the
gh
cli when creating a new releaseOn https://github.com/unjs/changelogen?tab=readme-ov-file#changelogen-gh-release:
Locally:
However when feeding the GH token manually it does work as expected:
Additional context
No response
Logs
No response
Tasks
The text was updated successfully, but these errors were encountered: