Repository navigation
chore: bring runtimes, dependencies and CI up to date; fix two bugs - #38
Merged
Merged
Conversation
Backend - Lambda runtime python3.9 -> python3.14. python3.9 reached end of support on 2025-12-15 and function updates are blocked from 2027-08-31. The handlers need no code changes. Frontend - next 16.2.6 -> 16.4.3 and react / react-dom 18.3.1 -> 19.3.1. react-bootstrap 2.10.10 declares react >=16.14 as its peer range. - Remove react-use-websocket; nothing imports it (App.js uses the browser WebSocket API). - Remove the postcss override; next 16.4.3 pins patched postcss 8.5.23. - Regenerate package-lock.json. Resolves all 26 open Dependabot alerts (next, sharp, postcss, nanoid, source-map-js, baseline-browser-mapping). - Declare engines.node >=20.9.0 (the minimum next 16.4 requires). CI and Dependabot - Pin actions to commit SHAs (checkout v7.0.1, cfn_nag v0.8.10). - Add cfn-lint, which flags deprecated Lambda runtimes (W2531). - Compile the handlers with Python 3.14. - Build the frontend on Node 24 with npm ci, alongside npm audit. - Add .github/dependabot.yml: grouped security updates and weekly minor/patch updates for npm, monthly updates for GitHub Actions. Docs - README requirements name Python 3.14 and Node.js 20.9+.
…chine - reportProgress: the GoneException handler compared the error code to the integer 410, but the code is the string "GoneException", so the stale-connection cleanup never ran and the function re-raised. Any GoneException now deletes the connection row and returns normally. - statemachine: the apigateway:invoke steps hardcoded "Stage": "Prod", so deploying with a different ApiStageName broke progress reporting. The stage now comes from a DefinitionSubstitution of ApiStageName. With the default value the rendered definition is unchanged.
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.
Summary
Brings the sample's runtimes, dependencies and CI up to date, and fixes two bugs in error and non-default-stage paths. The default order flow behaves as before.
Backend
python3.9->python3.14.python3.9reached end of support on 2025-12-15 and function updates are blocked from 2027-08-31. The handlers need no code changes.Frontend
next16.2.6 -> 16.4.3,react/react-dom18.3.1 -> 19.3.1.react-bootstrap2.10.10 declaresreact >=16.14as its peer range.react-use-websocket, which nothing imports (App.jsuses the browserWebSocketAPI).postcssoverride;next16.4.3 pins patchedpostcss8.5.23.package-lock.json. This resolves all 26 open Dependabot alerts (next,sharp,postcss,nanoid,source-map-js,baseline-browser-mapping).engines.node >=20.9.0, the minimumnext16.4 requires.CI and Dependabot
actions/checkoutv7.0.1,stelligent/cfn_nagv0.8.10).cfn-lintjob, which flags deprecated Lambda runtimes (W2531).npm ci, alongsidenpm audit --omit=dev..github/dependabot.yml: grouped security updates and weekly minor/patch updates for npm, monthly updates for GitHub Actions.Docs
Bug fixes
reportProgress: theGoneExceptionhandler compared the error code to the integer410, but the code is the string"GoneException". The stale-connection cleanup never ran and the function re-raised. It now deletes the connection row and returns normally.apigateway:invokesteps hardcoded"Stage": "Prod", so deploying with a differentApiStageNamebroke progress reporting. The stage now comes from aDefinitionSubstitutionsentry. With the defaultProd, the rendered definition is unchanged.Testing
npm audit --omit=dev: 0 vulnerabilities.npm ciandnpm run buildsucceed on Node 24.main; no console errors.sam buildwith Python 3.14 succeeds;sam local invoke MockGenerateLabelFunctionreturns the expected payload in thepython3.14container.cfn-lint: no findings.cfn_nag: 0 failures, the same 13 warnings asmain.reportProgresswith stubbed clients: a connected client gets the message as before; a 410 now deletes the DynamoDB row and returns, wheremainraisedGoneException.ApiStageName=Prodis identical tomain; withDev, everyapigateway:invokestep usesDev.ci.ymlanddependabot.ymlvalidate against the GitHub JSON schemas;actionlintreports no issues.