Adding opensearch test to lambda-handler#618
Merged
robertandremitchell merged 2 commits intoJun 11, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #618 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 47 47
Lines 2640 2640
=========================================
Hits 2640 2640 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
m-goggins
approved these changes
Jun 11, 2026
nickclyde
added a commit
that referenced
this pull request
Jun 11, 2026
## Summary - Bumps the root package version from `0.2.1` to `0.2.2`. Per `docs/releases.md`, merging to `main` triggers the release workflow to tag `v0.2.2`, build/publish the three Lambda images (`index`, `ttc`, `augmentation`) to GHCR and APHL ECR, and post the release to Slack. ## Changes since v0.2.1 - #624 — Update Schematron Model and Processor to use new/updated Schematron Error Messages from APHL - #618 — Adding opensearch test to lambda-handler - #617 — Revert "Remove Marcelle from CODEOWNERS" - #609 — fix: Bypass Docker layer cache when rebuilding for OS patches - #608 — refactor: Remove augmentation ABC - #607 — refactor: ruff data curation - #605 — Add coverage shortcut for unit tests - #599 — Increasing data-curation coverage - #598 — feat!: Remove configuration from Augmentation - #594 — Add Schematron validation to aws_e2e.sh - #593 — SPIKE: Embedding variability - #592 — typing in data curation folder and rest of repo - #590 — Add Embedding Vectors to Embedding Records for LOINC Updates - #588 — Pin external GitHub actions to specific commit SHAs - #580 — Extending ty checks to most of packages/ folder - #578 — refactor: Move some log statements closer to relevant code - #577 — Skip floating vX.Y / vX tags on APHL ECR push - #570 — feat!: Refactor TTC lambda function and condense saved models. - #569 — Rob/adding evaluator coverage test - #568 — Extending schematron validation in e2e tests (Dependabot bumps omitted; full notes are auto-generated on the GitHub Release.) Note: #570 and #598 are marked `feat!:` (breaking). If those warrant a minor bump instead, this can be re-cut as `0.3.0`. ## Test plan - [x] CI green on this PR - [ ] After merge: `release` workflow run on the merge commit is green - [ ] `git fetch --tags && git tag -l "v0.2.2"` shows the new tag - [ ] GitHub Release `v0.2.2` published with PR-list notes - [ ] APHL ECR has `v0.2.2` and `latest` tags for `index`, `ttc`, `augmentation` - [ ] Slack release-notifications channel received the release link
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
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.
Description
Noticed a small coverage gap, adding
Related Issues
Closes #[Link any related issues or tasks from your project management system.]
Additional Notes
[Add any additional context or notes that reviewers should know about.]
<--------------------- REMOVE THE LINES BELOW BEFORE MERGING --------------------->
Checklist
Please review and complete the following checklist before submitting your pull request:
Checklist for Reviewers
Please review and complete the following checklist during the review process: