fix: adding "vals" to GithubRelease changes for API and expanded assets #912
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.
With #907, we resolved an issue where GitHub release files were not being detected via autobump. Recent logs (e.g. https://circleci.com/api/v1.1/project/github/bioconda/bioconda-utils/44398/output/110/0?file=true&allocation-id=64e7a915cc25c03a3d0cf725-0-build%2FABCDEFGH) show this has changed and it is correctly detecting the version update. However, we are generating new errors now that are specifically caused by the PR submission (this was not previously tested, an oversight on my part):
This is caused by a lack of passing the
vals
fields through from the previous PR. Error was replicated locally via:With the very minor changes here,
vals
is passed through and we now get a full run without errors via dry-run:Hopefully, this is the last PR related to this issue!