Error: Command failed with exit code 1: git commit -m chore(release): 2.9.0 [skip ci] # [2.9.0](https://github.com/AlaskaAirlines/auro-select/compare/v2.8.5...v2.9.0) (2024-01-26) ### Features * **deps:** update dependencies and add SSR support [#166](https://github.com/AlaskaAirlines/auro-select/issues/166) [#167](https://github.com/AlaskaAirlines/auro-select/issues/167) ([38f02a8](https://github.com/AlaskaAirlines/auro-select/commit/38f02a8033456dc6e01dcb732f195745cea35a78)) > @aurodesignsystem/auro-select@2.9.0 preCommit > node scripts/pre-commit.mjs ╭ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ──────────────────────────────╮ Are you familiar with Auro's Definition of Done? Please be sure to review https://auro.alaskaair.com/definition-of-done before submitting your pull request to ensure that you are compliant. ╰─────────────────────────────── ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─╯ > @aurodesignsystem/auro-select@2.9.0 test > wtr --coverage Chrome: |██████████████████████████████| 0/1 test files | 0 passed, 0 failed Running tests... Running 1 test files... �[2K�[1A�[2K�[Gtest/auro-select.test.js: 🚧 Browser logs: Lit is in dev mode. Not recommended for production! See https://lit.dev/msg/dev-mode for more information. Element auro-select scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information. Element auro-dropdown scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information. An error was thrown in a Promise outside a test. Did you forget to await a function or assertion? Error: This `ChildPart` has no `parentNode` and therefore cannot accept a value. This likely means the element containing the part was manipulated in an unsupported way outside of Lit's control such that the part's marker nodes were ejected from DOM. For example, setting the element's `innerHTML` or `textContent` can do this. Error: This `ChildPart` has no `parentNode` and therefore cannot accept a value. This likely means the element containing the part was manipulated in an unsupported way outside of Lit's control such that the part's marker nodes were ejected from DOM. For example, setting the element's `innerHTML` or `textContent` can do this. at ChildPart._$setValue (node_modules/lit-html/src/lit-html.ts:1386:12) at TemplateInstance._update (node_modules/lit-html/src/lit-html.ts:1220:15) at ChildPart._commitTemplateResult (node_modules/lit-html/src/lit-html.ts:1574:50) at ChildPart._$setValue (node_modules/lit-html/src/lit-html.ts:1413:11) at render (node_modules/lit-html/src/lit-html.ts:2213:7) at AuroSelect.update (node_modules/lit-element/src/lit-element.ts:163:23) at AuroSelect.performUpdate (node_modules/@lit/reactive-element/src/reactive-element.ts:1441:13) at AuroSelect.performUpdate (src/auro-select.js:427:11) at AuroSelect.scheduleUpdate (node_modules/@lit/reactive-element/src/reactive-element.ts:1338:24) at AuroSelect.__enqueueUpdate (node_modules/@lit/reactive-element/src/reactive-element.ts:1310:24) An error was thrown in a Promise outside a test. Did you forget to await a function or assertion? Error: This `ChildPart` has no `parentNode` and therefore cannot accept a value. This likely means the element containing the part was manipulated in an unsupported way outside of Lit's control such that the part's marker nodes were ejected from DOM. For example, setting the element's `innerHTML` or `textContent` c

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.