Skip to content

Q10: use readable YXCleanType values (vac_and_mop / vacuum / mop) (#794) #2785

Q10: use readable YXCleanType values (vac_and_mop / vacuum / mop) (#794)

Q10: use readable YXCleanType values (vac_and_mop / vacuum / mop) (#794) #2785

Triggered via push March 22, 2026 18:14
Status Failure
Total duration 3m 14s
Artifacts

ci.yml

on: push
Matrix: test
Lint Commit Messages
12s
Lint Commit Messages
lint
16s
lint
Build Package
Build Package
Test Semantic Release
Test Semantic Release
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
Lint Commit Messages
You have commit messages with errors ⧗ input: Q10: use readable YXCleanType values (vac_and_mop / vacuum / mop) (#794) * refactor(q10): use readable YXCleanType values with legacy aliases * fix(cli): make clean mode option case insensitive * refactor(YXCleanType): move legacy values to a separate dictionary and update from_value method * test(YXCleanType): add tests for legacy clean type string aliases * refactor(YXCleanType): simplify clean type definitions and remove legacy alias support * test(YXCleanType): add tests for readable public values and compatibility with aliases * test(YXCleanType): add compatibility test for readable values in from_value method * test(q10): update clean type code mapping tests Co-authored-by: Allen Porter <allen.porter@gmail.com> * fix(q10): restrict clean mode cli choices * refactor(YXCleanType): remove legacy test for readable public values * test(YXCleanType): update test for readable values to use canonical names * test(YXCleanType): simplify test for readable values in from_value method --------- Co-authored-by: Allen Porter <allen.porter@gmail.com> ✖ type must be lower-case [type-case] ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
release
Generating and uploading digital attestations