Repository navigation
chore: release packages - #49
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 31, 2026 16:19
0cd42c8 to
01ad64c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
November 2, 2026 04:27
7369c3a to
a7a0ae5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 2, 2026 05:24
a7a0ae5 to
c652f29
Compare
JounQin
approved these changes
Nov 2, 2026
20 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
[email protected]
Minor Changes
#50
a7efb20Thanks @JounQin! - Addgcb pr --as-user <login>to create a pull request through the host opener using that person's~/.config/gh-<login>configuration;gcb issue create --as-user <login>uses the same route.--via-hostis gone: the login names the route and the account. The selected directory must exist before the request is made.#55
c47a3a5Thanks @JounQin! - Make the pull-request identity explicit: app installation token by default,--as-userwithout alogin for the broker's authorized user token, and
--as-user <login>for the host-opener route.#56
f4c8d71Thanks @JounQin! - Addgcb repo fork [owner/name]: create a fork under a person's account with--as-user(brokerauthorized user or host opener). The app identity cannot own a fork, so it is refused.
Patch Changes
28fa646Thanks @JounQin! - Fail loudly whenpr --threadsgets no review-thread report instead of printing nothing; a malformed,structurally incomplete, or missing-field GraphQL response is no longer reported as "no review
threads". Refused pull-request actions are audited as
pull-request, notcredential.a7efb20,c47a3a5,f4c8d71]:[email protected]
Minor Changes
#50
a7efb20Thanks @JounQin! - Addgcb pr --as-user <login>to create a pull request through the host opener using that person's~/.config/gh-<login>configuration;gcb issue create --as-user <login>uses the same route.--via-hostis gone: the login names the route and the account. The selected directory must exist before the request is made.#55
c47a3a5Thanks @JounQin! - Make the pull-request identity explicit: app installation token by default,--as-userwithout alogin for the broker's authorized user token, and
--as-user <login>for the host-opener route.#56
f4c8d71Thanks @JounQin! - Addgcb repo fork [owner/name]: create a fork under a person's account with--as-user(brokerauthorized user or host opener). The app identity cannot own a fork, so it is refused.
[email protected]
Minor Changes
#50
a7efb20Thanks @JounQin! - Addgcb pr --as-user <login>to create a pull request through the host opener using that person's~/.config/gh-<login>configuration;gcb issue create --as-user <login>uses the same route.--via-hostis gone: the login names the route and the account. The selected directory must exist before the request is made.#55
c47a3a5Thanks @JounQin! - Make the pull-request identity explicit: app installation token by default,--as-userwithout alogin for the broker's authorized user token, and
--as-user <login>for the host-opener route.#56
f4c8d71Thanks @JounQin! - Addgcb repo fork [owner/name]: create a fork under a person's account with--as-user(brokerauthorized user or host opener). The app identity cannot own a fork, so it is refused.
Patch Changes
#46
3475d35Thanks @JounQin! - Addgcb config editto open the broker configuration in$VISUAL/$EDITORand validate thesaved file.
#60
ceaf2beThanks @JounQin! - Classify invalid-proxy pull-request refusals with the request op in the audit log, and stop counting anempty comment body as omitted lines in
pr --threads.#57
28fa646Thanks @JounQin! - Fail loudly whenpr --threadsgets no review-thread report instead of printing nothing; a malformed,structurally incomplete, or missing-field GraphQL response is no longer reported as "no review
threads". Refused pull-request actions are audited as
pull-request, notcredential.Updated dependencies [
a7efb20,c47a3a5,f4c8d71]: