v1.0.1

PR #	Author	Title	Merged Date
#38	sparksam	Sanitize job titles when creating Docker containers and Kubernetes jobs Kubernetes does not allow space in labels. So it was causing a bug when creating pods with job titles containing space or some special characters.	2025-09-18
#37	chrisbendel	Audit packages and update	2025-09-22
#39	kswanson33	fix task definition not found exception Sometimes a task definition would be queried after it was already cleaned up. This didn't happen often but would crash the app when it did. I've moved the cleanup to happen after logs are sent so that the task definition will remain defined until then.	2025-10-06

v1.0.0

PR #	Author	Title	Merged Date
#36	sparksam	SHRIMP-54: Kubernetes Implementation & Trivy security configuration updates Implemented: - [x] Kubernetes workflow and enclave cleanup - [x] Send error statuses to Management app when error occurs - [x] Pull and manage reasearch containers - [x] Updated tests - [x] Trivy configurAtion update	2025-08-28
#34	sparksam	SHRIMP-117 SHRIMP-116 SHRIMP-83 SHRIMP-39 Implemented: - [x] SHRIMP-117: Add Vulnerability Scanner Trivy to CI/CD pipeline - [x] SHRIMP-116: Fix Critical/high vulnerabilities in Setup App - [x] SHRIMP-83: Run enclave in Docker on a VM - [x] SHRIMP-39: Start up the OpenStax Enclave with the Management App with all the apps locally	2025-07-30
#35	kswanson33	use log configuration for task to find log events	2025-07-21
#33	kswanson33	continue to search log groups if task not found	2025-07-03
#32	kswanson33	prevent logs from sending multiple times uses endpoint in safeinsights/management-app#285	2025-07-03
#31	philschatz	poll studies and failed jobs more frequently to reduce the QA and dev feedback time Refs SHRMP-110 [SHRMP-110]: https://openstax.atlassian.net/browse/SHRMP-110?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ	2025-06-24
#30	kswanson33	send error logs from task to toa	2025-06-17
#28	rnathuji	Remove BMA study fetch when starting poll We have thus far made a decision that when the SA is unable to access the BMA, it should fail loudly so we get a clear signal in deployments. Unfortunately, in practice it seems that we may lose BMA access in environments for various reasons. This change prevents the SA from cycling rapidly in failures so we can maintain "fail loudly" while avoiding high CPU and costs associated with immediately failing on launch.	2025-04-09
#35	kswanson33	use log configuration for task to find log events	2025-07-21
#35	kswanson33	use log configuration for task to find log events	2025-07-21