Repository navigation
chore: forward-merge main into next after 1.0.1 - #317
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The EdgeStore handler now rejects request bodies that are not sent as application/json, so cross-origin requests always need a CORS preflight. The edgestore-ctx cookie defaults to SameSite=Lax and HttpOnly, plus Secure over HTTPS or in production, and the encrypted context expires with the configured cookie maxAge instead of a fixed 30 days. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…talls Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop the per-request https flag from the adapters, the dispatcher request, init and getCookieConfig. Secure now defaults to on when NODE_ENV is production, the same for every adapter, and cookieConfig still overrides it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
trustPolicyIgnoreAfter (30 days) applies the trust check to fresh releases, where hijacked versions appear, so the semver/vite exclusions are no longer needed. next@16.4.1 is now well past the one-day release age gate, so its minimumReleaseAgeExclude entries are removed. Also trims the comments. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The defaults work without configuration, and the JSDoc on each cookie option already states its default. The changeset keeps the one override a cross-site frontend needs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Testing a production build over plain HTTP drops the Secure context cookie (Safari does so even on localhost), and uploads then fail with a bare "Missing edgestore-ctx cookie". The error and changeset now say how to opt out with secure: false. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci: harden the release pipeline and dependency installs
fix: harden the context cookie against cross-site requests
Bumps the github-actions group with 1 update: [pnpm/action-setup](https://github.com/pnpm/action-setup). Updates `pnpm/action-setup` from 6.0.10 to 6.1.0 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0977fd9...ea17c68) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/setup-go](https://github.com/actions/setup-go) from 6.5.0 to 7.0.0. - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](actions/setup-go@924ae3a...b7ad1da) --- updated-dependencies: - dependency-name: actions/setup-go dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 6.5.0 to 7.1.0. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@2499707...949feb2) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: 7.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/cache](https://github.com/actions/cache) from 5.1.0 to 6.1.0. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@caa2961...55cc834) --- updated-dependencies: - dependency-name: actions/cache dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
The SDK now runs beforeDelete on replacement targets, so the next-complete example no longer needs its own ownership check in beforeUpload. The docs keep one sentence per place a user meets the change, and the changeset is shorter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…key layout A custom `path` callback can place files with different router paths at the same key, so the shared layer can't assume an existing file has the upload's path. S3 and Azure now include the path only with the default layout; otherwise `canDelete` fails closed for buckets with path fields. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…thub-actions-dfc3086b10 chore(deps): bump pnpm/action-setup from 6.0.10 to 6.1.0 in the github-actions group
…tions/setup-go-7.0.0 chore(deps): bump actions/setup-go from 6.5.0 to 7.0.0
…tions/cache-6.1.0 chore(deps): bump actions/cache from 5.1.0 to 6.1.0
…tions/setup-node-7.1.0 chore(deps): bump actions/setup-node from 6.5.0 to 7.1.0
A "/" inside a path value or the browser-chosen file name lets different paths produce the same default key, so the key no longer proves the existing object's path. S3 and Azure now share one helper that reports the path only for the default layout with slash-free segments; otherwise the overwrite check fails closed like deletion does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
changesets/action v2 refuses to run against @changesets/cli 2.x. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci: migrate release workflow to changesets/action v2
Re-uploading an existing manualFileName now says which file already exists, both when the bucket has no beforeDelete and when beforeDelete refuses, instead of a generic replacement error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix: require beforeDelete to replace or overwrite files from the browser
Version Packages
Brings the security fixes (#308, #309), release pipeline hardening (#307, #316), action updates and the 1.0.1 version bump into next. In release.yml, keeps next's node-version-file pin from #305 and main's removal of the pnpm cache from publishing jobs (#307). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This branch was successfully deployed
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.
Summary
Forward-merges
mainintonext, asRELEASING.mddescribes. This brings the 1.0.1 release work tonext:beforeDeletefor replace/overwrite)changesets/actionv2 + Changesets CLI v3)One conflict, in
.github/workflows/release.yml: the three publishingsetup-nodesteps.nexthad switched them tonode-version-file: .nvmrcin #305, its Node 24.22.1 pin, whilemainhad removedcache: pnpmfrom them in #307. The resolution keeps both:Evidence
On the merge commit, with pnpm 11.15.1 and Node 24.22.1:
pnpm install --frozen-lockfile: passespnpm build: passespnpm typecheck: passespnpm test: 9/9 tasks passRisk and rollback
Door: Two-way. Revert the merge commit to undo. Merge with a merge commit, not a squash, so later forward merges stay clean.
Blast radius: Only the
nextbranch and its Vercel previews.nextis dormant (no.changeset/pre.json), so the release workflow skips publishing on push.🤖 Generated with Claude Code