Repository navigation
chore: version packages - #269
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 7, 2026 02:19
e051357 to
59a87c6
Compare
This branch has not been 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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@contentauth/c2pa-utilities@0.5.0
Minor Changes
e1dd252: Add Context options to configure trust-resource retries, HTTPS enforcement, and in-flight deduplication.
HTTPS enforcement rejects all redirects before contacting their targets and isolates strict requests from permissive in-flight requests. Document equivalent-policy request sharing and explicit undefined overrides of Context options. Completed responses are not cached; successful settings remain memoized only within each Context.
Patch Changes
9973341: Reuse in-flight trust-resource fetches across concurrent settings resolutions using the global fetch and the same URL and effective fetch policy, without caching completed responses. Keep custom fetch implementations isolated to avoid sharing requests across mutable wrapper contexts.
Apply a 30-second trust-resource deadline covering retries and response-body consumption. Timeouts reject waiting resolutions and allow subsequent fetch attempts without silently substituting trust data.
Validate numeric fetch options before fetching: reject non-finite and negative values, require a safe-integer retry count, and document option-specific zero behavior.
@contentauth/c2pa-node@0.10.1
Patch Changes
@contentauth/c2pa-web@0.16.1
Patch Changes