Re-enable old fee extensions in sandbox #2939
Merged
Conversation
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
weiminyu
approved these changes
Jan 21, 2026
Collaborator
weiminyu
left a comment
weiminyu
left a comment
There was a problem hiding this comment.
@weiminyu partially reviewed 22 files and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @gbrodman).
Now that we've passed the RST testing (or at least the EPP portion of it) we are no longer bound by the restriction to only use the fee extension version 1.0 on sandbox. For now, in order to avoid changing prod behavior, this does not enable advertisement of the fee extension version 1.0 in production. We can change this at any point in the future.
gbrodman
force-pushed
the
enableOldFeesAllEnvs
branch
from
2f4e158 to
2814aba
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now that we've passed the RST testing (or at least the EPP portion of it) we are no longer bound by the restriction to only use the fee extension version 1.0 on sandbox.
For now, in order to avoid changing prod behavior, this does not enable advertisement of the fee extension version 1.0 in production. We can change this at any point in the future.
For the most part, this PR just moves the tests from the production-simulating test classes back into the normal flow test class. We add a couple default-allocation-token tests to make sure that that behavior remains tested even if we delete the old fee extension tests in the future.
This change is