[CDTOOL-1144] Let profile accept service-limited tokens by jedisct1 · Pull Request #1856 · fastly/cli

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 · 2026-07-29T13:22:26Z

Change summary

fastly profile create, profile update and auth login validate a static token by looking up the current user, but that endpoint was recently made unavailable to service-limited tokens (a recent change), so these commands failed even with a valid token.

Fix that: tokens are now accepted as long as either /current_user or /tokens/self succeeds.

All Submissions:

Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes to Core Features:

Have you written new tests for your core changes, as applicable?
Have you successfully run tests with your changes locally?

User Impact

No behavior change for full-access tokens. Profiles created from a service-limited token won't display an email or account ID, but this is expected.

Are there any considerations that need to be addressed for release?

None. No breaking changes, no config format change.

When the "fastly profile create" command is run and provided an existing (static) token, and that token is service-limited, the GET /user/:id operation invoked by the CLI to validate the token failed because that endpoint is now unavailable to service-limited tokens. This was a recent behavior change. Fix that by reusing what we already did for the "profile update" command.

A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

rcaril

Looks great, great refactor with two minor / optional nits. Please also add a changelog entry :)

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

jedisct1 · 2026-07-29T15:09:17Z

(nit): the both-fail test only checks the error message - consider also verifying the token isn't saved to the config when validation fails (e.g. a Validator asserting GetAuthToken(...) is nil)

Done :)

jedisct1 · 2026-07-29T15:12:01Z

ChangeLog entry added. Not sure if that should be in "Enhancements" or "Bug fixes" (since it doesn't really fix a bug in the CLI itself).

rcaril

One suggestion for the changelog, otherwise looks good!

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

jedisct1 added 2 commits July 29, 2026 15:05

Accept service-limited tokens everywhere
16d3189
A token is now accepted whenever /current_user or /tokens/self responds successfully. In service-limited tokens the email and account ID are empty, so handle that properly.

jedisct1 requested a review from a team as a code owner July 29, 2026 13:22

jedisct1 requested a review from rcaril July 29, 2026 13:22

Add the actual error when token validation fails
b2cd1c9

rcaril requested changes Jul 29, 2026
View reviewed changes

Comment threadpkg/app/run.go
Comment threadpkg/commands/auth/login.go

Verify the token isn't saved to the config when validation fails
4f99260

Add a ChangeLog entry
215a4ba

rcaril reviewed Jul 29, 2026
View reviewed changes

Comment threadCHANGELOG.md Outdated

rcaril approved these changes Jul 29, 2026
View reviewed changes

Move changelog entry to the fixes section
869247f

jedisct1 merged commit 8e7de0a into mainJul 29, 2026
14 checks passed

jedisct1 deleted the fdenis/profilecreate branch July 29, 2026 16:00

BrewTestBot mentioned this pull request Aug 4, 2026
fastly 15.5.0 Homebrew/homebrew-core#297065
Merged

Uh oh!

Conversation

jedisct1 commented Jul 29, 2026

Change summary

Changes to Core Features:

User Impact

Are there any considerations that need to be addressed for release?

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

jedisct1 commented Jul 29, 2026

Change summary

Changes to Core Features:

User Impact

Are there any considerations that need to be addressed for release?

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

jedisct1 commented Jul 29, 2026

Change summary

Changes to Core Features:

User Impact

Are there any considerations that need to be addressed for release?

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

jedisct1 commented Jul 29, 2026

Uh oh!

Uh oh!

rcaril left a comment

Choose a reason for hiding this comment