fix: use non strict schema to allow some undefined behavior

[ChristopherHX]

• GitHub Actions doesn't use the newer strict schema in the service
• Tolerate more hallucinations

Provide Guidance

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	1		0	0.01s
✅ REPOSITORY	gitleaks	yes		no	2.36s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	9.08s
✅ REPOSITORY	secretlint	yes		no	1.08s
✅ REPOSITORY	trivy-sbom	yes		no	0.11s
✅ REPOSITORY	trufflehog	yes		no	4.32s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[ChristopherHX]

@jsoref What do you think?

This appends an informal error if schema fails.

I thought about adding strict validation after weak validation as warning, but the planner code doesn't have the context where the logger can be substituted... :(

Docu update here: nektos/act-docs#32

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.93%. Comparing base (5a80a04) to head (be575d3).
Report is 128 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #2524       +/-   ##
===========================================
+ Coverage   61.56%   74.93%   +13.36%     
===========================================
  Files          53       62        +9     
  Lines        9002    10013     +1011     
===========================================
+ Hits         5542     7503     +1961     
+ Misses       3020     1943     -1077     
- Partials      440      567      +127     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jsoref]

jsoref@jsoref-mbp winget-dsc % act --version
act version 0.2.69
jsoref@jsoref-mbp winget-dsc % act -l 2>&1|tail -3
Line: 37 Column 3: Failed to match on-sequence-strict: Line: 37 Column 3: Expected a sequence got mapping
Line: 37 Column 3: Failed to match on-mapping-strict: Line: 43 Column 5: Failed to match null: Line: 43 Column 5: Expected a scalar got mapping
Line: 43 Column 5: Failed to match pull-request-target-mapping: Line: 45 Column 5: Unknown Property tags-ignore

jsoref@jsoref-mbp winget-dsc % ~/code/nektos/act/dist/local/act --version
act version b253c5d
jsoref@jsoref-mbp winget-dsc % ~/code/nektos/act/dist/local/act -l
INFO[0000] Using docker host 'unix:///var/run/docker.sock', and daemon socket 'unix:///var/run/docker.sock'
WARN  ⚠ You are using Apple M-series chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠
Stage  Job ID        Job name        Workflow name   Workflow file    Events
0      spelling      Check Spelling  Spell Checking  spellCheck.yaml  push,pull_request_target
1      comment-push  Report (Push)   Spell Checking  spellCheck.yaml  push,pull_request_target
1      comment-pr    Report (PR)     Spell Checking  spellCheck.yaml  pull_request_target,push

I was expecting to see an error message...

In theory, I like these changes, but..., for reasons I don't understand, I'm not seeing them.

[ChristopherHX]

for reasons I don't understand, I'm not seeing them.

The error level has been lowered. Custom properties in on are no failure anymore.