Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use User.ID instead of User.Name in ActivityPub API for Person IRI (#23823) #23905

Merged
merged 1 commit into from
Apr 4, 2023

Conversation

GiteaBot
Copy link
Contributor

@GiteaBot GiteaBot commented Apr 4, 2023

Backport #23823 by @wxiaoguang

Thanks to @trwnh

Close #23802

The ActivityPub id is an HTTPS URI that should remain constant, even if the user changes their name.

…o-gitea#23823)

Thanks to @trwnh

Close go-gitea#23802

The ActivityPub id is an HTTPS URI that should remain constant, even if
the user changes their name.
@GiteaBot GiteaBot added type/bug skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. labels Apr 4, 2023
@GiteaBot GiteaBot added this to the 1.19.1 milestone Apr 4, 2023
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Apr 4, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 4, 2023
@jolheiser jolheiser merged commit 9836b7d into go-gitea:release/v1.19 Apr 4, 2023
@zeripath
Copy link
Contributor

zeripath commented Apr 4, 2023

This is breaking and should not have been merged in to 1.20 or 1.19.

The swagger description for the old path should have been kept in place and the new one added.

You cannot just drop API at whim.

@lunny
Copy link
Member

lunny commented Apr 4, 2023

The previous implementation is not correct because user's login name could be changed by admin.

@wxiaoguang
Copy link
Contributor

Please help to show a case about how it breaks.

  1. If the user is using an old API client, the old handlers are still there, no break.
  2. If the user is using a new API client, the API calls are all generated by new swagger document, no break.

If there is really a breaking case, we can simply revert.

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Aug 1, 2023
@techknowlogick techknowlogick deleted the backport-23823-v1.19 branch September 9, 2023 05:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants