Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: sync with w3up repo #119

Merged
merged 6 commits into from
Jan 16, 2025
Merged

chore: sync with w3up repo #119

merged 6 commits into from
Jan 16, 2025

Conversation

@fforbeck fforbeck requested a review from alanshaw January 15, 2025 13:46
@fforbeck fforbeck self-assigned this Jan 15, 2025
We were defaulting to the production URL unless a `receiptsEndpoint` was
given in the options, and then never providing one. Passing it along
would probably be the better solution, but there are a lot of places to
get that wrong as things stand right now. It's not clear to me where the
receipt URL really should live--eg., whether it should properly be part
of the connection config.
In cloudflare workers the request fails with: `The 'mode' field on
'RequestInitializerDict' is not implemented.`.

Detecting cloudflare environment as advised by cloudflare:
https://developers.cloudflare.com/workers/runtime-apis/web-standards/#navigatoruseragent
@fforbeck fforbeck marked this pull request as ready for review January 15, 2025 17:04
@fforbeck fforbeck changed the title chore: sync with w3up repo - WIP chore: sync with w3up repo Jan 16, 2025
packages/w3up-client/README.md Outdated Show resolved Hide resolved
packages/w3up-client/package.json Outdated Show resolved Hide resolved
@fforbeck fforbeck requested a review from alanshaw January 16, 2025 13:48
Copy link
Member

@alanshaw alanshaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One docs fix but otherwise LGTM

packages/w3up-client/README.md Outdated Show resolved Hide resolved
@fforbeck fforbeck merged commit d86e52c into main Jan 16, 2025
17 checks passed
alanshaw pushed a commit that referenced this pull request Jan 20, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.0.3](upload-client-v1.0.2...upload-client-v1.0.3)
(2025-01-16)


### Other Changes

* sync with w3up repo
([#119](#119))
([d86e52c](d86e52c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
alanshaw pushed a commit that referenced this pull request Jan 20, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.1.3](client-v1.1.2...client-v1.1.3)
(2025-01-16)


### Other Changes

* sync with w3up repo
([#119](#119))
([d86e52c](d86e52c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Port changes made in w3up that do not yet exist in upload-service.
2 participants