Cypress frequently throws a [warning] Unexpected input

[DlgSHi]

We have set-up the cypress run for GitHub Actions using your examples. But yesterday it starts failing with en errors as below:

Link to Actions for our project

@bahmutov , @brian-mann any thoughts ?

[DlgSHi]

An issue was with different env parameters sent from difference GitHub Actions jobs. Fixed with implementing docker container as env.

[leosuncin]

I believe is because those inputs are not defined in action.yml

github-action/action.yml

Lines 5 to 25 in 4fdf3ee

	inputs:
	record:
	description: 'Sends test results to Cypress Dashboard'
	required: false
	default: false
	config:
	description: 'Set configuration values. Separate multiple values with a comma. The values set here override any values set in your configuration file.'
	required: false
	config-file:
	description: 'Path to a JSON file where configuration values are set.'
	required: false
	default: cypress.json
	env:
	description: 'Sets Cypress environment variables'
	required: false
	browser:
	description: 'Name of the browser to use'
	required: false
	command:
	description: 'Command that overrides cypress run'
	required: false

[jennifer-shehane]

Have this issue been resolved? Can this issue be closed?

[jebendfds]

@jennifer-shehane We are still experiencing this issue. Your documentation says to use the working directory parameter to specify the cypress folder in monorepos, yet the parameter is unrecognized.

Can you elaborate more on your solution @DlgSHi ?

[DlgSHi]

The solution is about setting the same env for every job on the GitHub Actions using docker image. But not about warnings

[prescottprue]

@jennifer-shehane No, I do not think it is yet resolved. As @leosuncin mentioned, I believe it is due to the settings not being in action.yml - I made a PR to include a number of the missing inputs

[craig-dae]

We have started having this problem yesterday. All pipelines have started failing. We can't merge to master anymore. This is with a production app.

We could use either a fix or a workaround please.

[prescottprue]

@craig-dae I provided a PR for fixing the warnings mentioned above, so now it should just be a matter of getting it merged. If it ends up taking a little while longer I can merge in to master of my fork so that can be pointed to in the meantime

[craig-dae]

@prescottprue So actually, I am thinking my issue is different, and I should re-open my issue report. I thought that these warnings were causing my issue, but I just looked, and these warnings have been appearing long before my pipeline stopped working.

[calebeby]

Thanks @prescottprue for your fix, looks great! It would be great if someone from Cypress could merge that

[DlgSHi]

No more warnings as above, thanks :)
One more new warning appears :(

[DlgSHi]

Made a PR to fix that warning

[DlgSHi]

After release v.1.24.3 - no more warnings in console :) Thanks guys, closing an issue

[myildizCH]

Sometimes it is just enough to clean everything and reinstall. Please follow the steps below if you can't find any solution:
• Go to the project directory
• Remove the node_modules directory: rm -rf node_modules.
• Remove package-lock.json file: rm package-lock.json
• Clear the cache: npm cache clean --force
• Run npm install --verbose