Skip to content

chore(deps): bump rcpchgrowth to 4.6.4 - #293

Merged
pacharanero merged 2 commits into
livefrom
chore/bump-rcpchgrowth-4.6.4
Sep 6, 2026
Merged

pacharanero merged 2 commits into
livefrom
chore/bump-rcpchgrowth-4.6.4

Conversation

@pacharanero

@pacharanero pacharanero commented Sep 6, 2026 •

Copy link
Copy Markdown
Member

Summary

  • bump the calculation engine from rcpchgrowth 4.6.2 to 4.6.4
  • consume the package-level mid-parental-height input validation added in fix: validate mid-parental height inputs rcpchgrowth-python#107
  • normalize release-specific provenance versions/commits in committed regression goldens, while preserving and testing the full provenance structure, producer names, and growth-reference identity

Regression evidence

  • captured exact, unnormalized 881-case snapshots before (4.6.2) and after (4.6.4)
  • status distribution unchanged: 487 responses at 200 and 394 at 422
  • 317 cases changed; an automated leaf-level comparison found zero unexpected fields
  • all exact snapshot changes are limited to provenance.calculation_engine.version, provenance.calculation_engine.commit, and the expected provenance.api_server.commit
  • no numerical, response-shape, status, or content-type changes

Golden provenance policy

  • committed goldens retain provenance, growth_reference, producer names, and all structural requirements
  • only API-server and calculation-engine version/commit values are replaced with stable sentinels during acceptance and comparison
  • focused provenance tests continue to verify the real runtime versions, commits, names, schemas, and pass-through behaviour
  • dependency snapshots remain exact and unnormalized for upgrade investigations

Validation

  • s/test: 1074 passed, 1 skipped
  • regression suite: all 881 cases pass against normalized goldens
  • s/compatibility-test: 47/47 pass for both legacy-7.5.2 and provenance-v1 profiles
  • installed container package: rcpchgrowth 4.6.4
  • one-time golden normalization verified mechanically: 317 files changed, zero non-sentinel differences

The unrelated local .gitignore change is not included.

Follow-up to closed issue #267.

Adopt the released package validation and code-quality work. The
881-case before/after sweep shows no numerical, status, content-type,
or response-shape changes; 317 responses change only calculation
engine and API commit provenance. Accept those reviewed goldens.

The full server suite and both React compatibility profiles pass.
Keep the provenance object, producer names, and growth-reference
identity in every regression golden, but replace release-specific
version and commit values with stable sentinels when accepting and
comparing goldens. Focused provenance tests continue to verify the
real runtime versions, commits, names, schema, and references.

Dependency snapshots remain exact and unnormalized for upgrade
review. This removes routine golden churn from package and server
version bumps without weakening behavioural API coverage.
@pacharanero
pacharanero merged commit d90b96f into live Sep 6, 2026
1 check passed
@pacharanero
pacharanero deleted the chore/bump-rcpchgrowth-4.6.4 branch September 6, 2026 16:44
@rcpch-prout

rcpch-prout Bot commented Sep 6, 2026

Copy link
Copy Markdown

Seen on LIVE (merged by @pacharanero 3 minutes and 21 seconds ago) Please check your changes!

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

@pacharanero @mbarton: the live deployment and APIM OpenAPI import completed successfully. Please verify the API operations and policies in the Azure portal.

Deployment: https://github.com/rcpch/digital-growth-charts-server/actions/runs/34046389032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant