rm support for deprecated reqStep in req/resp #6857
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It also attempts to address the issue in https://github.com/status-im/nimbus-eth2/actions/runs/12829462835/job/35775570006 where after the update to nondeprecated
upload-artifact@v4
:The CI had begun failing, and would fail consistently starting in a couple of weeks, using
upload-artifact@v3
, due to this deprecation. This@v3
version was relying on behavior intentionally changed in v4 and the maintainers are fairly adament that, no, there's no direct/drop-in way to use v4 in the v3 manner, nor should there be.Regarding
overwrite: false
, it is possible to configure that totrue
, but actions/upload-artifact#506 suggests that doesn't adequately resolve this, and:The two
linux-amd64
jobs are potentially functioning in this parallel manner. Enablingoverwrite: true
is a still-possible step, but not the most elegant or, apparently, robust, approach.https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error presumably would just cause this not to be an error, but also, well.
scripts/repo_paths.sh
was not used.