Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 12, 2026

This PR contains the following updates:

Package Change Age Confidence
@algolia/requester-fetch ^4.20.0^4.25.3 age confidence
@atproto/api (source) ^0.18.7^0.18.16 age confidence
@effect/platform (source) ^0.92.1^0.94.1 age confidence
@effect/platform-node (source) ^0.98.3^0.104.0 age confidence
@effect/workflow (source) ^0.11.2^0.16.0 age confidence
@octokit/plugin-rest-endpoint-methods ^16.1.0^16.1.1 age confidence
@octokit/types ^15.0.0^15.0.2 age confidence
algoliasearch (source) ^4.20.0^4.25.3 age confidence
dfx ^0.126.0^0.127.0 age confidence
effect (source) ^3.18.4^3.19.14 age confidence
groq-sdk ^0.33.0^0.37.0 age confidence
octokit ^5.0.3^5.0.5 age confidence

Release Notes

bluesky-social/atproto (@​atproto/api)

v0.18.16

Compare Source

Patch Changes

v0.18.15

Compare Source

Patch Changes

v0.18.14

Compare Source

Patch Changes

v0.18.13

Compare Source

Patch Changes

v0.18.12

Compare Source

Patch Changes

v0.18.11

Compare Source

Patch Changes

v0.18.10

Compare Source

Patch Changes
Effect-TS/effect (@​effect/platform)

v0.94.1

Compare Source

Patch Changes
  • #​5936 65e9e35 Thanks @​schickling! - Document subtle CORS middleware allowedHeaders behavior: when empty array (default), it reflects back the client's Access-Control-Request-Headers (permissive), and when non-empty array, it only allows specified headers (restrictive). Added comprehensive JSDoc with examples.

  • #​5940 ee69cd7 Thanks @​kitlangton! - HttpServerResponse: fix fromWeb to preserve Content-Type header when response has a body

    Previously, when converting a web Response to an HttpServerResponse via fromWeb, the Content-Type header was not passed to Body.stream(), causing it to default to application/octet-stream. This affected any code using HttpApp.fromWebHandler to wrap web handlers, as JSON responses would incorrectly have their Content-Type set to application/octet-stream instead of application/json.

  • Updated dependencies [488d6e8]:

    • effect@​3.19.14

v0.94.0

Compare Source

Minor Changes
Patch Changes

v0.93.8

Compare Source

Patch Changes

v0.93.7

Compare Source

Patch Changes

v0.93.6

Compare Source

Patch Changes

v0.93.5

Compare Source

Patch Changes

v0.93.4

Compare Source

Patch Changes

v0.93.3

Compare Source

Patch Changes

v0.93.2

Compare Source

Patch Changes

v0.93.1

Compare Source

Patch Changes

v0.93.0

Compare Source

Patch Changes
Effect-TS/effect (@​effect/platform-node)

v0.104.0

Compare Source

Patch Changes

v0.103.0

Compare Source

Patch Changes

v0.102.0

Compare Source

Patch Changes

v0.101.2

Compare Source

Patch Changes

v0.101.1

Compare Source

Patch Changes

v0.101.0

Compare Source

Patch Changes

v0.100.0

Compare Source

Patch Changes

v0.99.0

Compare Source

Minor Changes
  • #​5606 24a1685 Thanks @​tim-smart! - backport @​effect/cluster from effect v4

    @​effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

Effect-TS/effect (@​effect/workflow)

v0.16.0

Compare Source

Patch Changes

v0.15.2

Compare Source

Patch Changes

v0.15.1

Compare Source

Patch Changes

v0.15.0

Compare Source

Minor Changes
Patch Changes

v0.14.0

Compare Source

Minor Changes
Patch Changes

v0.13.1

Compare Source

Patch Changes
  • #​5821 2519056 Thanks @​tim-smart! - add DurableQueue module

    A DurableQueue wraps a PersistedQueue, providing a way to wait for items
    to finish processing using a DurableDeferred.

    import { DurableQueue, Workflow } from "@​effect/workflow"
    import { Effect, Schema } from "effect"
    
    // Define a DurableQueue that can be used to derive workers and offer items for
    // processing.
    const ApiQueue = DurableQueue.make({
      name: "ApiQueue",
      payload: {
        id: Schema.String
      },
      success: Schema.Void,
      error: Schema.Never,
      idempotencyKey(payload) {
        return payload.id
      }
    })
    
    const MyWorkflow = Workflow.make({
      name: "MyWorkflow",
      payload: {
        id: Schema.String
      },
      idempotencyKey: ({ id }) => id
    })
    
    const MyWorkflowLayer = MyWorkflow.toLayer(
      Effect.fn(function* () {
        // Add an item to the DurableQueue defined above.
        //
        // When the worker has finished processing the item, the workflow will
        // resume.
        //
        yield* DurableQueue.process(ApiQueue, { id: "api-call-1" })
    
        yield* Effect.log("Workflow succeeded!")
      })
    )
    
    // Define a worker layer that can process items from the DurableQueue.
    const ApiWorker = DurableQueue.worker(
      ApiQueue,
      Effect.fn(function* ({ id }) {
        yield* Effect.log(`Worker processing API call with id: ${id}`)
      }),
      { concurrency: 5 } // Process up to 5 items concurrently
    )
  • Updated dependencies [ebfbbd6]:

v0.13.0

Compare Source

Minor Changes
Patch Changes

v0.12.5

Compare Source

Patch Changes

v0.12.4

Compare Source

Patch Changes

v0.12.3

Compare Source

Patch Changes

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

Patch Changes

v0.12.0

Compare Source

Minor Changes
  • #​5606 24a1685 Thanks @​tim-smart! - backport @​effect/cluster from effect v4

    @​effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

tim-smart/dfx (dfx)

v0.127.0

Compare Source

Note: Version bump only for package dfx

0.126.1 (2025-10-12)

Note: Version bump only for package dfx

groq/groq-typescript (groq-sdk)

v0.37.0

Compare Source

Full Changelog: v0.36.0...v0.37.0

Features
Chores
  • GitHub Terraform: Create/Update .github/workflows/code-freeze-bypass.yaml [skip ci] (eda725d)

v0.36.0

Compare Source

Full Changelog: v0.35.0...v0.36.0

Features
Chores
  • GitHub Terraform: Create/Update .github/workflows/code-freeze-bypass.yaml [skip ci] (b37d3e0)

v0.35.0

Compare Source

Full Changelog: v0.34.0...v0.35.0

Features

v0.34.0

Compare Source

0.34.0 (2025-10-16)

Full Changelog: v0.33.0...v0.34.0

Features
Chores
  • internal: remove .eslintcache (5023bb0)
  • internal: use npm pack for build uploads (fba1e53)

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team and Adammatthiesen as code owners January 12, 2026 01:07
@renovate renovate bot force-pushed the renovate/artemis-artemis-dependencies branch 2 times, most recently from c5c99d3 to b26f496 Compare January 17, 2026 04:58
@renovate renovate bot force-pushed the renovate/artemis-artemis-dependencies branch from b26f496 to 9119021 Compare January 18, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant