[codex] suspend legacy notify deprecation warning#21151
Closed
abhinav-oai wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
Superseded by #21152, which does the full revert instead of the narrower warning-only rollback. |
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
1 participant
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.
Why
The legacy
notifydeprecation notice currently reaches users whose configuration comes from the computer use plugin. We should avoid surfacing that warning until the plugin has migrated offnotify, so users do not get a warning they cannot act on yet.What
notifyTesting
just fmtcargo test -p codex-core emits_deprecation_notice_for_experimental_instructions_file