Removed the headers argument passed to 'fetch' in step one#85
Merged
larsoner merged 5 commits intoscientific-python:masterfrom Sep 16, 2025
Merged
Removed the headers argument passed to 'fetch' in step one#85larsoner merged 5 commits intoscientific-python:masterfrom
larsoner merged 5 commits intoscientific-python:masterfrom
Conversation
Removed header with credential info from step 1 fetch
Update index.js
Collaborator
|
Seems reasonable to me. I'll merge and cut another release |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Originally the api token was being passed to fetch in step one, where the workflow is being polled for job information, which seems to result in 401 errors.
The URL being constructed for that section can be examined without the API token, so I stopped the header being passed to that fetch, and my problem (which I misdiagnosed in issue #83) is now fixed.
Closes #83