Skip to content

feat: Update documentation surrounding CI and API keys#516

Open
easymac wants to merge 2 commits intomainfrom
mc/api-keys-changes
Open

feat: Update documentation surrounding CI and API keys#516
easymac wants to merge 2 commits intomainfrom
mc/api-keys-changes

Conversation

@easymac
Copy link
Contributor

@easymac easymac commented Mar 20, 2026

Status

READY

Description

  • Add a new dedicated API Keys page documenting the full lifecycle of API keys: creation, usage, expiration options, permission levels, revocation, migration from login:ci, and security details.
  • Rewrite the shared CI authentication snippet to direct users to the console-based API key flow instead of the deprecated shorebird login:ci command. Includes a migration callout noting login:ci tokens remain valid until March 2027.
  • Update the FAQ entry for CI usage to point users to the console for API key creation rather than the old CLI flow.

@easymac easymac requested review from eseidel and tomarra March 23, 2026 19:55
## Migrating from `shorebird login:ci`

The `shorebird login:ci` command is deprecated. Existing tokens generated by
`login:ci` will continue to work until March 2027, but we recommend replacing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`login:ci` will continue to work until March 2027, but we recommend replacing
`login:ci` will continue to work until September 2026, but we recommend replacing

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I agree on the 6 months timeline. Biggest thing is making sure we end up putting this into multiple customer comms like the newsletter and other emails

cc @dawn-ducky

The `SHOREBIRD_TOKEN` is a secret and should not be checked in to your source
control or shared publicly.
The `shorebird login:ci` command is deprecated. Existing tokens generated by
`login:ci` will continue to work until March 2027, but new tokens should be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`login:ci` will continue to work until March 2027, but new tokens should be
`login:ci` will continue to work until September 2026, but new tokens should be

Copy link
Contributor

@eseidel eseidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing!

authenticated. In order to authenticate with Shorebird in CI, you will need to
generate a CI token.
Most Shorebird functionality, like creating releases and patches, requires
authentication. To authenticate in CI, create an API key from the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
authentication. To authenticate in CI, create an API key from the
authentication. To authenticate in your CI, create an API key from the

We kind of need to start talking about a users CI system vs. ours since we have a CI product as well.

:::

Example:
:::note
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feels kinda weird to have 3 callouts in a row.


export SHOREBIRD_TOKEN="$SHOREBIRD_TOKEN" && shorebird patch android
```
On Pro and Business plans, you can restrict an API key to **Release & Patch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this just link to the orgs section that talks about roles instead of duplicating the content?

- **Full access** — the key has the same permissions as your account. Available
on all plans.
- **Release & Patch only** — the key can create releases and patches, but cannot
manage apps, organizations, members, or billing. Available on Pro and Business
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing with a link to the orgs/roles section would be good here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants