QPPSE-4799: PY26 Historical Benchmarks #1006
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
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
pkasarski
changed the title
michelingle
approved these changes
Jan 12, 2026
michelingle
left a comment
michelingle
left a comment
There was a problem hiding this comment.
Reviewed this on Friday and it looks good!
ckawell-sb
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Tickets & Documents
https://jira.cms.gov/browse/QPPSE-4799
Description
Add historical benchmarks for PY26.
What type of PR is this?
🔴 IMPORTANT: Add required labels
At least one of each type of PR label should be added for checks to pass.
notes:*version:*Patch versions are code-only changes, with no data updates.
Minor versions are data changes, such as updates to the measures-data.json files.
Major versions are annual and tied to a PY's data becoming avaliable, determined by QPPA's PO.
Added tests?
Added to documentation?