The macOS release reaches the upload stage after successful signing, notarization and ZIP verification, then fails with Unexpected end of JSON input. For an unversioned bucket, AWS CLI can return exit code 0 with empty stdout instead of {}. Treat that successful empty response as an unversioned configuration and explicitly request JSON output. Malformed responses, versioned/suspended buckets and command failures still stop before upload.
Validation: all 32 affected upload tests pass, including eight added cases for empty/whitespace/object responses and malformed data. ESLint and git diff checks pass. Reproduced the underlying behavior with the installed AWS CLI against a local HTTP server returning an empty S3 VersioningConfiguration: exit 0, empty stdout and stderr; no real credentials or bucket mutations involved.
Run 1335 completed build, signing, notarization and packaged download verification. Its upload failed at GetBucketVersioning before writing any objects. No new secrets or bucket settings are needed.
After merge, the selected release tag must include this upload-code fix; a manual workflow on main with an old tag would still check out the old script. For the unpublished 0.1.0 release, recreate macos-v0.1.0 at the merged main commit to trigger a new run. A published version must never be replaced. This PR does not move any tag.
Ticket: https://kanbangit.de/projects/1/tickets/58
Base and PR target: main, checked out and pulled with --ff-only at b0cc9dad14746ac65baf9b399974e74bc1df2843 before creating fix/KAN-58-empty-s3-versioning.
KAN-58 remains In Progress until the real S3 release and the user's installation/start acceptance succeed; destination remains Review.
The macOS release reaches the upload stage after successful signing, notarization and ZIP verification, then fails with `Unexpected end of JSON input`. For an unversioned bucket, AWS CLI can return exit code 0 with empty stdout instead of `{}`. Treat that successful empty response as an unversioned configuration and explicitly request JSON output. Malformed responses, versioned/suspended buckets and command failures still stop before upload.
Validation: all 32 affected upload tests pass, including eight added cases for empty/whitespace/object responses and malformed data. ESLint and git diff checks pass. Reproduced the underlying behavior with the installed AWS CLI against a local HTTP server returning an empty S3 VersioningConfiguration: exit 0, empty stdout and stderr; no real credentials or bucket mutations involved.
Run 1335 completed build, signing, notarization and packaged download verification. Its upload failed at GetBucketVersioning before writing any objects. No new secrets or bucket settings are needed.
After merge, the selected release tag must include this upload-code fix; a manual workflow on main with an old tag would still check out the old script. For the unpublished 0.1.0 release, recreate `macos-v0.1.0` at the merged main commit to trigger a new run. A published version must never be replaced. This PR does not move any tag.
Ticket: https://kanbangit.de/projects/1/tickets/58
Base and PR target: `main`, checked out and pulled with `--ff-only` at `b0cc9dad14746ac65baf9b399974e74bc1df2843` before creating `fix/KAN-58-empty-s3-versioning`.
KAN-58 remains In Progress until the real S3 release and the user's installation/start acceptance succeed; destination remains Review.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The macOS release reaches the upload stage after successful signing, notarization and ZIP verification, then fails with
Unexpected end of JSON input. For an unversioned bucket, AWS CLI can return exit code 0 with empty stdout instead of{}. Treat that successful empty response as an unversioned configuration and explicitly request JSON output. Malformed responses, versioned/suspended buckets and command failures still stop before upload.Validation: all 32 affected upload tests pass, including eight added cases for empty/whitespace/object responses and malformed data. ESLint and git diff checks pass. Reproduced the underlying behavior with the installed AWS CLI against a local HTTP server returning an empty S3 VersioningConfiguration: exit 0, empty stdout and stderr; no real credentials or bucket mutations involved.
Run 1335 completed build, signing, notarization and packaged download verification. Its upload failed at GetBucketVersioning before writing any objects. No new secrets or bucket settings are needed.
After merge, the selected release tag must include this upload-code fix; a manual workflow on main with an old tag would still check out the old script. For the unpublished 0.1.0 release, recreate
macos-v0.1.0at the merged main commit to trigger a new run. A published version must never be replaced. This PR does not move any tag.Ticket: https://kanbangit.de/projects/1/tickets/58
Base and PR target:
main, checked out and pulled with--ff-onlyatb0cc9dad14746ac65baf9b399974e74bc1df2843before creatingfix/KAN-58-empty-s3-versioning.KAN-58 remains In Progress until the real S3 release and the user's installation/start acceptance succeed; destination remains Review.