aeoess-aps: narrow the 0.9.0 revocation note per #178 - #195
Merged
imran-siddique merged 1 commit intoSep 14, 2026
Merged
imran-siddique merged 1 commit into
imran-siddique merged 1 commit into
Conversation
"cannot be re-observed" and "cannot be re-run" were stronger than what was established. Both files already state the reason, so only the modal changes.
|
🔴 Contributor Check: HIGH
Automated check by AgenTrust Contributor Check. |
github-actions
Bot
added
the
needs-review:HIGH
imran-siddique
approved these changes
Sep 14, 2026
1 task
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
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.
Closes the tightening left on #178. "cannot be re-observed at 0.10.0" was stronger than what was established.
verify_recordrefuses the record on schema grounds before the revocation path runs, which both files already state, so only the modal verb changes.README:
It cannot be re-observed on this exporter's record at 0.10.0becomesIt was not re-evaluated at 0.10.0. Rest of the sentence unchanged.integration.yaml:They cannot be re-run on this exporter's record at 0.10.0becomesThey were not re-run on this exporter's record at 0.10.0. Rest unchanged.No other change. Tier, roles,
tested_againstand the CI jobs are untouched. Localvalidate_integrations.pyreports 37 integrations, 0 failures, andgenerate_integration_index.py --checkis clean.One other question while this is here. On #178 the exact head was already run end to end against the released versions now recorded in
tested_against. If that run already satisfies the repo's Verified criterion, happy for the tier to be flipped during review. If you want a fresh run against current main first, that's fine too, the reproduction steps are unchanged.