You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v3, codecov/uploader was used and it had an excessive list of possible config locations (a matrix of different filenames and dirs). With v4 and codecov/codecov-cli, though, that list was replaced with just a single possibility.
In other words, codecov/codecov-action@v4 changed the config path defaults without telling anyone:
The old defaults were to look up config filename variants with and without a leading dot, and with 3- and 4-letter extension variants, under the current working directory, .github/ subfolder and dev.
All my repos have the config in their respective roots called .codecov.yml, which worked without any problems for years across all the previous action versions v1/v2/v3 and with manual invocations before that.
With the upgrade to v4, it's not being detected:
warning - 2024-02-01 23:18:58,826 -- Config file codecov.yml not found, or is not a file. Ignoring config.
The text was updated successfully, but these errors were encountered:
In v3,
codecov/uploader
was used and it had an excessive list of possible config locations (a matrix of different filenames and dirs). With v4 andcodecov/codecov-cli
, though, that list was replaced with just a single possibility.In other words,
codecov/codecov-action@v4
changed the config path defaults without telling anyone:The old defaults were to look up config filename variants with and without a leading dot, and with 3- and 4-letter extension variants, under the current working directory,
.github/
subfolder anddev
.All my repos have the config in their respective roots called
.codecov.yml
, which worked without any problems for years across all the previous action versions v1/v2/v3 and with manual invocations before that.With the upgrade to v4, it's not being detected:
warning - 2024-02-01 23:18:58,826 -- Config file codecov.yml not found, or is not a file. Ignoring config.
The text was updated successfully, but these errors were encountered: