-
Notifications
You must be signed in to change notification settings - Fork 195
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
Drop the submitter field from serialized updates. #3144
Merged
mergify
merged 10 commits into
fedora-infra:develop
from
bowlofeggs:update-no-submitter
Apr 13, 2019
Merged
Drop the submitter field from serialized updates. #3144
mergify
merged 10 commits into
fedora-infra:develop
from
bowlofeggs:update-no-submitter
Apr 13, 2019
Conversation
This file contains 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
bowlofeggs
added
API
Issues related to Bodhi's REST API
High priority
These issues are higher priority than normal
Backwards incompatible
The proposed change is backwards incompatible and should wait for the next major release
labels
Apr 11, 2019
pypingou
approved these changes
Apr 11, 2019
Bodhi has been adding a non-existing field, submitter, to serialized versions of updates for compatibility with Bodhi 1. Bodhi 1 went EOL a long time ago, and this data is redundant with the update.user.name field that also appears in all serialized updates. Signed-off-by: Randy Barlow <randy@electronsweatshop.com>
bowlofeggs
force-pushed
the
update-no-submitter
branch
from
April 12, 2019 20:51
e07de13
to
2429b3e
Compare
This patch is planned for inclusion in the upcoming 4.0.0 release: #3221 |
Bodhi 4.0.0 beta is built and deployed to staging: https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi-pre-release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
API
Issues related to Bodhi's REST API
Backwards incompatible
The proposed change is backwards incompatible and should wait for the next major release
High priority
These issues are higher priority than normal
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.
Bodhi has been adding a non-existing field, submitter, to
serialized versions of updates for compatibility with Bodhi 1.
Bodhi 1 went EOL a long time ago, and this data is redundant with
the update.user.name field that also appears in all serialized
updates.
Signed-off-by: Randy Barlow randy@electronsweatshop.com