Skip to content

chore: version packages - #1000

Merged
PabloCastellano merged 1 commit into
mainfrom
changeset-release/main
Jul 3, 2026
Merged

chore: version packages#1000
PabloCastellano merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

@blobscan/docs@0.3.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

@blobscan/rest-api-server@0.16.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/blob-storage-manager@3.0.0
    • @blobscan/blob-propagator@3.0.0
    • @blobscan/api@3.0.0
    • @blobscan/db@0.29.0
    • @blobscan/env@0.4.0
    • @blobscan/rollups@3.0.0
    • @blobscan/syncers@0.6.7

@blobscan/web@0.54.0

Minor Changes

  • #1001 2865527 Thanks @PJColombo! - Add a banner announcing the migration to IPFS-based blob storage

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/blob-storage-manager@3.0.0
    • @blobscan/api@3.0.0
    • @blobscan/db@0.29.0
    • @blobscan/env@0.4.0
    • @blobscan/rollups@3.0.0

@blobscan/api@3.0.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/blob-storage-manager@3.0.0
    • @blobscan/blob-propagator@3.0.0
    • @blobscan/db@0.29.0
    • @blobscan/env@0.4.0
    • @blobscan/rollups@3.0.0

@blobscan/blob-propagator@3.0.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/blob-storage-manager@3.0.0
    • @blobscan/db@0.29.0

@blobscan/blob-storage-manager@3.0.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@blobscan/db@0.29.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

@blobscan/env@0.4.0

Minor Changes

  • #998 74b33ba Thanks @PJColombo! - Implement IpfsStorage.storeBlob via the blobscan-ipld push endpoint

    IpfsStorage can now write blobs (previously read-only): _storeBlob
    POSTs the blob plus its beacon/execution context to the blobscan-ipld
    service's POST /blob endpoint and persists the returned data_cid as the
    reference. To carry the extra fields the endpoint requires (commitment,
    tx hash, blob index, slot, epoch, block number, block hash), a new
    optional BlobContext is threaded through BlobStorage.storeBlob,
    BlobStorageManager, the propagator's BlobPropagationInput, and the
    indexer. The context is optional at the storage interface so other
    backends are unaffected; IpfsStorage asserts its presence at runtime.
    finalize is always sent as false since epoch completeness can't be
    known per blob.

    IPFS can now be selected as PRIMARY_BLOB_STORAGE (it was previously
    rejected as write-incapable). The write endpoint lives at a different
    base URL than the read gateway, so a new IPFS_STORAGE_IPLD_URL env var
    configures it; it's passed to IpfsStorage as a dedicated ipldUrl and
    is required when IPFS is the primary storage.

    IpfsStorage's health check now targets the blobscan-ipld service's
    /readyz endpoint when a write URL (ipldUrl) is configured, since that
    service owns the kubo client and the write path; read-only deployments
    (gateway only) still probe the IPFS gateway directly.

@blobscan/blob-propagation-jobs-cli@0.2.20

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/blob-propagator@3.0.0
    • @blobscan/db@0.29.0
    • @blobscan/env@0.4.0

@blobscan/stats-aggregation-cli@0.2.19

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@blobscan/auth@0.0.30

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@blobscan/optimism-decoder@0.1.23

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@blobscan/rollups@3.0.0

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@blobscan/syncers@0.6.7

Patch Changes

  • Updated dependencies [74b33ba]:
    • @blobscan/db@0.29.0

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.46%. Comparing base (39301fc) to head (b9fde5f).

Additional details and impacted files 
@@            Coverage Diff             @@
##             main    #1000      +/-   ##
==========================================
- Coverage   83.48%   83.46%   -0.02%     
==========================================
  Files         190      190              
  Lines       15081    15081              
  Branches     1465     1464       -1     
==========================================
- Hits        12590    12587       -3     
- Misses       2491     2494       +3

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from b9fde5f to 8ce475d Compare July 2, 2026 13:45
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8ce475d to df1daa8 Compare July 3, 2026 18:27
@PabloCastellano
PabloCastellano merged commit 150e956 into main Jul 3, 2026
@PabloCastellano
PabloCastellano deleted the changeset-release/main branch July 3, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@PabloCastellano