Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: storacha/ucanto
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: server-v10.1.0
Choose a base ref
...
head repository: storacha/ucanto
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: server-v10.2.0
Choose a head ref
  • 7 commits
  • 22 files changed
  • 3 contributors

Commits on Jan 22, 2025

  1. fix: upgrade dependencies (#366)

    depends on:
    
    * [x] ipld/js-dag-ucan#97
    alanshaw authored Jan 22, 2025
    Configuration menu
    Copy the full SHA
    bf6274c View commit details
    Browse the repository at this point in the history
  2. chore: release main (#367)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    github-actions[bot] authored Jan 22, 2025
    Configuration menu
    Copy the full SHA
    0f8dcf6 View commit details
    Browse the repository at this point in the history

Commits on Feb 12, 2025

  1. docs: fix example in README.md (#286)

    Copy-pasted some example code in the UCAN workshop. This fix made it work: the invocations are each individual arguments, not an array.
    
    Wondering though if the array form would be more intuitive when batching multiple invocations - in the old docs it would be `connection.execute(invocations)`, in the working code it's `connection.execute(...invocations)`.
    Frando authored Feb 12, 2025
    Configuration menu
    Copy the full SHA
    688680e View commit details
    Browse the repository at this point in the history

Commits on Feb 13, 2025

  1. fix: infinite recursion with unknown attestation (#368)

    If proofs contain an attestation that is not issued by the service authority then `claim(...)` will recurse indefinitely.
    alanshaw authored Feb 13, 2025
    Configuration menu
    Copy the full SHA
    d94496a View commit details
    Browse the repository at this point in the history
  2. feat: validate attestation from another service (#369)

    This PR implements #268 
    
    Specifically, we are changing the `did:web:web3.storage` service DID to `did:web:up.storacha.network` and want to allow attestations issued by `did:web:web3.storage` to still be considered valid.
    
    resolves #268 
    closes #267
    alanshaw authored Feb 13, 2025
    Configuration menu
    Copy the full SHA
    bac2cb0 View commit details
    Browse the repository at this point in the history
  3. feat: allow alternative audience for server (#371)

    This PR adds a new server option `audience`, which allows the server to accept invocations for audiences other than the service itself.
    
    This option was already available (and continues to be available) on a per handler basis (via `provideAdvanced`), it takes precedence over the new global server audience.
    
    Concretely, the DID for web3.storage is changing, but we want to be able to accept invocations targeting the old DID without having to configure every single handler.
    alanshaw authored Feb 13, 2025
    Configuration menu
    Copy the full SHA
    d793091 View commit details
    Browse the repository at this point in the history
  4. chore: release main (#370)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    github-actions[bot] authored Feb 13, 2025
    Configuration menu
    Copy the full SHA
    aeb3ca5 View commit details
    Browse the repository at this point in the history
Loading