Version Packages - #1533
Merged
Atchyut Preetham Pulavarthi (theonly1me) merged 1 commit intoAug 28, 2026
Merged
Conversation
Atchyut Preetham Pulavarthi (theonly1me)
marked this pull request as ready for review
August 28, 2026 16:19
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Fahd Ahsan (Dhaaaf)
approved these changes
Aug 28, 2026
Atchyut Preetham Pulavarthi (theonly1me)
merged commit Aug 28, 2026
0eadd54
into
main
7 checks passed
Atchyut Preetham Pulavarthi (theonly1me)
deleted the
changeset-release/main
branch
August 28, 2026 16:20
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
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.
This PR was opened by hand because the
Version PRjob still cannot open it.The failure has moved on since #1531, so this is a third distinct problem in the same step rather than the one that PR described:
The 'client-id' ... input must be set to a non-empty string— the job declared no environmentInvalid keyData/ERR_OSSL_ASN1_NOT_ENOUGH_DATA— the private key did not parse401 A JSON web token could not be decodedSo the PEM on
release-versionwas repaired between yesterday and now, and it is no longer malformed. What is left is that the JWT it signs is rejected by GitHub onGET /repos/qawolf/cli/installation, which is what you get when the private key does not belong to the app named byclient-id.The
releaseenvironment holds a pair that does work —Publishused it to ship1.17.0an hour ago. So the fix is to copy bothQA_WOLF_OPS_CLIENT_IDandQA_WOLF_OPS_PRIVATE_KEYfromreleasetorelease-versionas a matched pair. Replacing only the key is what leaves it in this state. This PR does not do that, and the next merge carrying a changeset fails the same way until someone does.The contents here are exactly what
changeset versionproduces: the changeset consumed,CHANGELOG.mdextended, and the version moved to1.17.1.Merging this releases
1.17.1.has_changesetsbecomes false, so the brokenVersion PRjob is skipped entirely andPublishtakes over frommainusing thereleaseenvironment, which works.Releases
@qawolf/cli@1.17.1
Patch Changes
qawolf runner runnow falls back toQAWOLF_ENVIRONMENTwhen neither--env-idnor--env-fileis passed, so the one export that already sets a default forqawolf flowscovers a runner run too.--env-idstill wins over it, and--env-filesuppresses it so a run reading a dotenv file is not handed a second environment on top. The run reports on stderr which environment it picked up.