Skip to content

Update dependency @eventcatalog/core to v4 - #29

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eventcatalog-core-4.x
Open

Update dependency @eventcatalog/core to v4#29
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eventcatalog-core-4.x

Conversation

@renovate

@renovate renovate Bot commented Jul 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@eventcatalog/core 2.55.5 → 4.10.14 age confidence

Release Notes

event-catalog/eventcatalog (@​eventcatalog/core)

v4.10.14

Compare Source

Patch Changes
  • 089076b: Render Protovalidate and custom field annotations in the Protobuf schema viewer, and add property hover feedback across schema formats.

v4.10.13

Compare Source

Patch Changes
  • 8ec3e6c: Show the Assistant by default with bring-your-own-model setup guidance and an option to hide it. Refresh the Ask and search UI, add the keyboard shortcut, and prevent focus from entering the closed assistant sidebar.

v4.10.12

Compare Source

Patch Changes

  • 55c993d: Add build-time link validation for static catalogs and fix broken resource reference links

    • New linkValidation config option checks internal links and anchors in generated HTML after static builds (warns by default, can be set to error or ignore, supports ignore globs)
    • <ResourceRef> now links teams, users, and custom pages without a version segment, resolves owners to the correct users or teams page, and resolves messages to the collection they actually live in
    • Catalog discovery, schema loading, design discovery, and the linter scanner now exclude node_modules so dependency example catalogs are never loaded as catalog resources
    • Default template containers now declare owners

  • Updated dependencies [55c993d]

v4.10.11

Compare Source

Patch Changes
  • 79d6dcd: Fix DomainGrid command and query links in domain/system architecture views. SSR (and system pages) now hydrate service sends/receives so links use /docs/commands|queries|events/... and the resource name, instead of defaulting missing collections to events.

v4.10.10

Compare Source

Patch Changes
  • 50888dc: Load schema explorer content, examples, producers, and consumers on demand instead of embedding every version and relationship in the page. Preserve the producer label in the list and full relationships in the selected schema. Fetch comparison versions when needed, with loading states, retries, and cached requests.

v4.10.9

Compare Source

Patch Changes
  • 65d02d1: Stop prerendering Field Usage pages for messages with no field-level lineage. The sidebar already hid those links; static builds still emitted a full HTML page per event/command/query. On a synthetic catalog of 8 domains / 64 services / 640 events this removed 640 pages and cut total HTML from 199.45 MB to 163.58 MB (−18%, −35.9 MB). Also compact NodeGraph island props so docs/visualiser pages no longer embed markdown bodies or hydrated producer/consumer trees.
  • d2a6402: Use dagre's tight-tree ranker for large node graphs so domain and architecture maps layout in hundreds of milliseconds instead of several seconds.
  • Updated dependencies [d2a6402]

v4.10.8

Compare Source

Patch Changes

v4.10.7

Compare Source

Patch Changes

  • 48b79c2: fix(embed): hide catalog chrome and fill the viewport when embedding pages

    • Hide the vertical nav, header and resource sidebar on any page rendered with ?embed=true
    • Give the visualiser, architecture graph, system context map, schema explorer, schema detail and discover pages a full-height embedded viewport (CSS driven, replacing the old post-load inline height scripts)
    • Support ?theme=light / ?theme=dark alongside embed=true so an embed can pick its own theme without overwriting the user's saved catalog preference

v4.10.6

Compare Source

Patch Changes
  • 076c612: feat(core): redesigned mermaid and PlantUML diagram controls. Diagrams now have hover-revealed pan/zoom/reset controls with smooth transitions, a fullscreen modal viewer (drag, scroll and pinch to zoom, keyboard shortcuts) and placement / actions options for code blocks and <MermaidFileLoader />

v4.10.5

Compare Source

Patch Changes
  • b2dc248: chore(core): add content hash, plan, ci and command fields to build telemetry

v4.10.4

Compare Source

Patch Changes
  • 7192a9b: Fix mermaid iconPacks so extra Iconify collections (e.g. openmoji, mdi) load from their own packs instead of always using logos.
  • 1592c57: fix(auth): pin issuer on the GitHub auth provider so RFC 9207 iss validation no longer fails with unexpected "iss" (issuer) response parameter value when an older @​auth/core copy is hoisted in user projects

v4.10.3

Compare Source

Patch Changes

  • 0acf0d8: fix(core): embedded <ArchitectureGraph/> not rendering in static builds and 404s on domain System Diagram visualiser pages

    • The MDX <ArchitectureGraph/> placeholder and its island are now paired by document order instead of a render-time occurrence counter — Astro can invoke MDX component functions more than once per tag, which drifted the counter and left the island unable to find its portal div (the graph silently rendered nothing).
    • /visualiser/domains/:id/:version/systems-context pages were never generated because the guard looked systems up by their hydrated entry id — it now reads the hydrated system entries directly, matching the sidebar's guard.

v4.10.2

Compare Source

Patch Changes
  • f2f2c6b: fix type errors in sidebar builders and dictionary term edit URL resolution, and run type checks in CI

v4.10.1

Compare Source

Patch Changes
  • ab6aa90: feat(core): fade in the architecture graph on mount instead of popping in after hydration
  • 75cd12d: feat(core): new <ArchitectureGraph/> MDX component to embed the D3 architecture graph in resource and custom documentation pages, focused on the page's resource

v4.10.0

Compare Source

Minor Changes

  • af02bfc: feat(core): customize any resource's sidebar with a sidebar.json file

    Drop a sidebar.json next to any resource's index.mdx (domains, systems, services, agents, messages, flows, containers, entities, data products and ADRs) to fully define that resource's sidebar. Compose predefined $sections (kept live as your catalog changes) with your own groups of resource references ([[service|order-service]]), documentation ([[doc|guides/onboarding]]), specifications ([[spec|openapi.yml]]), schemas ([[schema|order-placed]]) and links (with {id}/{version}/{collection} placeholders). Groups nest, accept an explicit collapsed initial state, and versioned resources inherit the resource folder's sidebar. Unresolvable tokens and doc/spec/schema references fail the build with an error naming the file and the valid options.

    The sidebar also renders as a consistent docs-style tree: every group is collapsible with carets on the right, nested groups indent under a guide line, item counts are removed, the selected item stays in view after navigation, and scroll position is remembered.

v4.9.0

Compare Source

Minor Changes
  • 679c0d8: fix(core): silence Astro 7.2.8 content reference errors for message schemas, fix dark-theme syntax colours on first load of light-mode schema pages, and stop TanStack Table warnings on the directory pages
Patch Changes

v4.8.4

Compare Source

Patch Changes
  • 5e77f94: fix(core): stop treating entities owned by a domain as external in the entity map

v4.8.3

Compare Source

Patch Changes
  • adb80fd: Fix LikeC4 diagrams in Vite dev by resolving likec4:plugin/ virtual modules without a \0 prefix.

v4.8.2

Compare Source

Patch Changes

v4.8.1

Compare Source

Patch Changes

v4.8.0

Compare Source

Minor Changes
  • 2d47c4a: Support V-prefixed integer resource versions such as V1, V2, and V10 across version comparison, lookup, federation, and snapshots. Prerelease versions now follow strict semver rules instead of being coerced to their stable version.
Patch Changes

v4.7.12

Compare Source

Patch Changes
  • 1deed7d: Show version-specific producers and consumers in the sidebar for historical messages.
  • 4cab4e0: Remove unused NestedSideBar SearchBar leftover code. Catalog search is unchanged: the header SearchModal and Discover grid filter are still in place.

v4.7.11

Compare Source

Patch Changes
  • 19439c8: Fix service and agent visualiser context menus linking container nodes to /entities/… instead of /containers/….

v4.7.10

Compare Source

Patch Changes

  • 6917590: Fix legacy generated documentation pills being unreadable in dark mode.

  • 3167265: fix(core): dev command crashing on Windows with regex_error(error_escape)

    The file watcher interpolated raw Windows backslash paths into its ignore
    glob, which @​parcel/watcher compiles with std::regex. Depending on the
    characters in the project path (e.g. a folder starting with x produced an
    invalid \x escape), this crashed npm run dev on startup. Paths are now
    normalized to forward slashes before building the glob.

v4.7.9

Compare Source

Patch Changes
  • c186d1e: Fix indexed search so ubiquitous language terms are searchable.

v4.7.8

Compare Source

Patch Changes
  • 74f6e23: Require the built-in Federation workflow to use the offline EventCatalog Enterprise entitlement instead of the Scale entitlement.

v4.7.7

Compare Source

Patch Changes
  • 2669f4b: Fix LikeC4 virtual module imports by resolving LikeC4 package subpaths from the catalog workspace.

v4.7.6

Compare Source

Patch Changes
  • b9321e6: Clarify that the built-in Federation workflow uses the EventCatalog Commercial License, ship the mixed-license terms with the core package, and enforce the existing Scale entitlement for every configured federation run.

v4.7.5

Compare Source

Patch Changes

  • fc71bc8: Add ESLint-style --verbose federation diagnostics for asset collisions and missing-resource references, with structured attributes, gray rule IDs, and consolidated problem counts.

    Remove the incomplete federation reference mode so all configured sources are consistently hydrated.

  • ac6aa66: Federation now restores the previous output when a run fails part way through. The federated resources directory, managed public assets, and eventcatalog.lock are snapshotted before the update and rolled back if hydration, public asset composition, or lock writing throws, so a failed federate no longer leaves the catalog in a half-written state.

  • 55a9c8e: Clarify the federation lock file log message to reflect that it records resolved source state, not just pinned commits

  • b68efb2: Federation diagnostics are now configurable per rule. Set federation.rules in eventcatalog.config.js to off, warn, or error for any federation/* rule, and add a new federation/unresolved-version warning when a resource references a version that does not exist. Remote references are resolved against resources owned by the central catalog before diagnostics are applied, and warning counts remain visible when errors coexist.

  • Updated dependencies [fc71bc8]

v4.7.4

Compare Source

Patch Changes

  • 653219a: Make federated custom components available through @catalog/components, with local catalog components taking precedence.

  • 653219a: Support local filesystem catalogs as federation sources using the file: protocol.

    Ignore generated dist and .eventcatalog-core resources when indexing catalogs.

  • Updated dependencies [653219a]

v4.7.3

Compare Source

Patch Changes
  • 74bd3ce: Make federated custom components available through @catalog/components, with local catalog components taking precedence.

v4.7.2

Compare Source

Patch Changes

v4.7.1

Compare Source

Patch Changes
  • 0546a63: fix(core): show AsyncAPI parser errors instead of a blank page when a specification fails to parse

v4.7.0

Compare Source

Minor Changes

  • cd55298: feat(core): render node graphs for channels

    Channel nodes offer a "Focus node" link to /visualiser/channels/{id}/{version}, but that
    route was never generated, so the link 404'd. For the same reason <NodeGraph /> on a channel
    documentation page rendered empty.

    Channels are now registered as a graph root in both places, and have their own graph showing the
    producers and messages that publish into the channel, the services and agents that consume from
    it, and any channels it routes to or is routed from. Channel documentation sidebars now also
    include an Architecture → Map link to the channel graph when the visualiser is enabled, and
    every channel in a routed chain exposes the standard resource context menu. Navigating between a
    channel's map and documentation now also keeps the channel sidebar selected.
    The focused channel is highlighted with the same persistent viewing border as other resource nodes.
    Channel maps resolve complete routing chains, so messages enter through their producer channel,
    pass through intermediate channels, and reach consumers through their configured channel without
    incorrect direct edges to the focused channel.

Patch Changes

v4.6.3

Compare Source

Patch Changes
  • f59c821: Add the eventcatalog federate CLI command. Reads federation.sources from the catalog config, fetches and indexes each configured GitHub source, resolves the combined graph, then hydrates federated content and public assets into the local catalog. Includes a content-addressed cache (--no-cache to bypass), pinned source commits in a lockfile, and ownership conflict reporting.
  • Updated dependencies [f59c821]

v4.6.2

Compare Source

Patch Changes

v4.6.1

Compare Source

Patch Changes
  • 20f51e0: Resources pages now list every resource directly attached to a domain (subdomains, systems, agents and data products alongside services, flows, entities and messages), and the sidebar Resources link appears whenever any of those exist. Service sidebar links are versioned again, and sidebar icons render at a consistent size.
  • 9a1bf7a: Keep the Browse section expanded while continuing to auto-collapse other large sidebar groups.
  • 91e8fc2: chore(core): bump astro and @​astrojs dependencies to their latest patch/minor releases
  • b6569aa: fix(core): update js-yaml to patch denial-of-service vulnerabilities

v4.6.0

Compare Source

Minor Changes

  • 3ee5549: feat(core): load catalog content from federated source directories

    Astro content collections now also scan federated/*/ so resources pulled in from
    federated catalog sources (services, domains, subdomains, resource docs and doc
    categories, ubiquitous language, users and teams) are picked up alongside the
    local catalog.

Patch Changes

v4.5.2

Compare Source

Patch Changes

v4.5.1

Compare Source

Patch Changes
  • d8f460d: fix(core): type wire links as tuples for astro check

v4.5.0

Compare Source

Minor Changes
  • ba27fe3: feat(core): add opt-in architecture graph — a catalog-wide force-directed graph at /visualiser/graph, enabled via visualiser.architectureGraph.enabled

v4.4.1

Compare Source

Patch Changes
  • 87862ef: updated auth/core version

v4.4.0

Compare Source

Minor Changes
  • 9ab9991: feat(core): astro-compress is now an optional peer dependency, install it in your catalog to use compress: true. Top level sidebar groups now stay expanded.

v4.3.4

Compare Source

Patch Changes
  • b1f3308: Improve sidebar navigation group collapsing, persistence, and layout scrolling

v4.3.3

Compare Source

Patch Changes
  • 04e5d19: Add stable, versionless URLs for the latest service's specifications, changelog, and attached documentation.

v4.3.2

Compare Source

Patch Changes

v4.3.1

Compare Source

Patch Changes
  • ee68c2a: fix(sidebar): use stable collapse keys for ADR status groups so collapse state persists correctly

v4.3.0

Compare Source

Minor Changes
  • c73c813: Add scoped MCP servers for domains and systems, with an mcp.enabled configuration option to disable the built-in server.

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes
  • eef46fc: Add a navigation loading indicator so users get feedback during slower (e.g. SSR) page transitions instead of the page appearing unresponsive.

v4.2.4

Compare Source

Patch Changes

v4.2.3

Compare Source

Patch Changes

v4.2.2

Compare Source

Patch Changes
  • 8850fcf: Suppress the Astro getStaticPaths() ignored in dynamic page router warning during builds and extract the Astro output filters into a dedicated, tested module

v4.2.1

Compare Source

Patch Changes
  • 3d39871: Fix changelog file diff resolution for versioned resources in SSR deployments.
  • ac932a9: Suppress Astro's empty optional collection messages when previewing or starting EventCatalog while preserving other warnings.
  • 5f3ce55: Fix the raw Markdown resource endpoints resolving catalog files from the server working directory in SSR deployments.

v4.2.0

Compare Source

Minor Changes
  • 6bd170f: Allow services, domains, and agents to document messages triggered by any received message and show both sides of those relationships in message sidebars and node graphs. Messages with documented trigger relationships include a dedicated Trigger paths page with one visual row per path and its optional scenarios; messages without paths do not generate the page. The SDK supports trigger pointers and includes domains when resolving message producers and consumers. Message, service, and data store visualizers now keep the currently viewed resource visibly marked as the graph's focus, and resource context menus can focus another node in its own map. Edge labels now render above graph edges so intersecting paths do not obscure their text.
Patch Changes

v4.1.5

Compare Source

Patch Changes
  • afc9ebf: fix(core): serve proper favicons instead of the logo image

v4.1.4

Compare Source

Patch Changes
  • 3a64d3a: fix(core): toolkit pages no longer inherit the default app content wrapper, so they can control their own layout and padding

v4.1.3

Compare Source

Patch Changes
  • a4caa45: Count custom pages and custom API routes in build analytics resource inventory

v4.1.2

Compare Source

Patch Changes

  • c4df67f: fix(core): builds failing with TypeError: Missing parameter: id when trailingSlash: true is set

    Astro 7.0.4 (withastro/astro PR #​17224) changed route patterns for dynamic file
    endpoints (e.g. /docs/teams/[id].md) to never accept a trailing slash, but the
    prerender path generator still appends one when trailingSlash: 'always' is
    configured. The generated path (/docs/teams/customer-platform.md/) no longer
    matches the route pattern, so static builds crash. A Vite plugin now patches
    Astro's param extraction to retry with the trailing slash flipped when no route
    pattern matches — a no-op on unaffected Astro versions and once the regression
    is fixed upstream.

v4.1.1

Compare Source

Patch Changes
  • c769012: feat(create-eventcatalog): optionally install EventCatalog Skills when scaffolding a new project, and surface the skills repo in the CLI banner

v4.1.0

Compare Source

Minor Changes
  • 80b0ddc: Custom pages: .astro and API route files in your catalog's pages/ directory are now served as routes under a configurable prefix (pages.prefix, defaults to custom). Requires the Scale plan.

v4.0.7

Compare Source

Patch Changes
  • a68d3a2: Fix the AI assistant API URL when EventCatalog is deployed with a custom base path (#​1345).
  • 9c6ead6: Schema Explorer version comparison now lets you pick any two versions to diff using From/To selectors instead of only showing consecutive-version diffs
  • 37bb4c9: Resolve JSON Schema $ref pointers (local and remote) when rendering remote JSON schemas, so referenced definitions are inlined instead of shown as unresolved $ref values.
  • Updated dependencies [0983132]
  • Updated dependencies [f963964]

v4.0.6

Compare Source

Patch Changes
  • 7ca87f7: Fix SchemaViewer portal targeting when multiple schemas share the same id on a page, so each schema renders into its correct container.

v4.0.5

Compare Source

Patch Changes
  • d6da676: Add a domain type filter (root domains / subdomains) to the Discover table and show subdomains nested under their parent domain in the name column.

v4.0.4

Compare Source

Patch Changes
  • cb103f0: Persist Discover table filters in the URL so searches, filters, and toggles survive page reloads and can be shared via link

v4.0.3

Compare Source

Patch Changes
  • eec436c: Add custom documentation tools (getCustomDocs, searchCustomDocs, getCustomDoc) to AI Chat and MCP Server, with section-level full-text search powered by MiniSearch

v4.0.2

Compare Source

Patch Changes
  • a74a736: Restrict EntityMap MDX component collection prop to domains or services

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

  • 728ca67: Add support for a new systems collection. Systems are a versioned resource that can be defined in any folder (including inside domains), rendered as documentation pages, and listed in the sidebar with their own icon and color. Systems can group services, flows, entities, data stores (containers), and diagrams, have their own architecture overview page (/architecture/systems/[id]) listing their entities, services, external integrations, data stores, and flows, be visualised as an architecture map, be browsed and filtered on a dedicated discover page (/discover/systems), and be targeted by architecture decision records (appliesTo: [{ type: 'system' }]). Domains can reference one or more systems, which are listed in the domain sidebar, rendered as expandable sections on the domain's architecture page (listing the system's services, like subdomains, with external services shown under "External Integrations"), and merged into the domain's architecture map (each referenced system's services are grouped within the domain graph). Teams and users can own systems, which are surfaced on their profile pages.

    Systems can also declare relationships to other systems (each with an optional version and label), which power a new Context Diagram visualiser (/visualiser/systems/[id]/[version]/context, linked from the system sidebar under Architecture). Starting from a system, the diagram walks its relationships outward to build the reachable neighbourhood of systems, rendering each as a node (showing its service, entity, and data store counts) connected by labelled edges. Clicking a system node opens that system's architecture map.

    Systems support a scope of internal (default) or external. External systems represent third-party/SaaS systems you integrate with (e.g. "Resend", "Stripe") and are shaded and badged as "External System" in the Context Diagram.

    Systems can also declare actors — people or roles that interact with the system (e.g. a Customer or Support Agent). Each actor has an id (used to de-duplicate the same actor across systems), an optional name/label, and a direction (inbound = actor → system, e.g. "logs into"; outbound = system → actor, e.g. "sends notifications to"). Actors are rendered as nodes on the Context Diagram connected to their system by a labelled, directional edge.

Minor Changes
  • cc936ab: Add configurable navigation groups for the vertical sidebar. You can now define custom navigation groups and items via navigation.groups in your eventcatalog.config.ts, including custom labels, Lucide icons, hrefs, external links, active-state matching, and top/bottom positioning. This replaces the previous sidebar visibility config.
  • f02e737: Add a dedicated "Top level diagrams" navigation group that surfaces the System Context Map below top-level domains in the sidebar.
  • e1c3984: Upgrade to Astro 7 and migrate markdown/MDX config to the new unified processor API
Patch Changes
  • 6f1790b: Replace the resource-specific Browse sidebar links with a single Discover link and add a Kind filter to discover pages for switching between available resource collections.
  • bea8571: Rebuild the create-eventcatalog default template with a new e-commerce catalog (domains, systems, services, messages) and fix the collapsed vertical nav brand link alignment.
  • 15aabba: Fix dev watcher incorrectly matching generated files when IGNORE_BUILD_ARTIFACTS is set. Build-artifact exclusions are now skipped in dev mode, since Astro's watcher uses picomatch against the pattern array where negated patterns caused unrelated generated files to match.
  • a99dc45: Remove the Export to PDF / print feature and make diagram version comparison available to everyone (no longer gated behind the Scale plan)
  • 86148d9: Add systems support to AI Chat, catalog tools, and sidebar navigation. The chat panel now recognises system pages and resources, the AI tools accept the systems collection, the custom documentation page renders the System Context Map when a domain has systems, and the System section in the sidebar shows the System Context Map when systems exist.
  • d64cfab: Add systems support to the SDK. Systems are a new resource type that can group services, flows, entities, and containers, and can be nested within domains. Includes helpers to read and write systems, add resources to a system, write resources directly into a system, and add systems to domains.
  • Updated dependencies [9949f9f]
  • Updated dependencies [728ca67]
  • Updated dependencies [d64cfab]

v3.48.4

Compare Source

Patch Changes

v3.48.3

Compare Source

Patch Changes
  • 2bb0759: Improve node graph performance by deferring dagre layout when composing sub-graphs and using Map-based de-duplication for nodes and edges

v3.48.2

Compare Source

Patch Changes
  • 38287a4: Sort ADRs in the sidebar by resource name instead of date

v3.48.1

Compare Source

Patch Changes

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • 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 force-pushed the renovate/eventcatalog-core-4.x branch from b394aab to d2c8034 Compare July 9, 2026 08:10
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch from d2c8034 to 9db94f3 Compare July 17, 2026 20:27
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch 2 times, most recently from fe9bc3c to c8ad3ed Compare July 29, 2026 08:05
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch 3 times, most recently from 2f8de36 to 58984b1 Compare August 8, 2026 07:31
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch 2 times, most recently from 810171e to bc275a7 Compare August 22, 2026 03:55
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch 2 times, most recently from cc2ceec to 1653675 Compare September 5, 2026 04:06
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch 2 times, most recently from 2d3b7c5 to b0a5e70 Compare September 13, 2026 16:02
@renovate
renovate Bot force-pushed the renovate/eventcatalog-core-4.x branch from b0a5e70 to a600cc3 Compare September 19, 2026 14:47
@renovate

renovate Bot commented Sep 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "strict-peer-dependencies". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.3.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-19T14_46_59_758Z-debug-0.log

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.

0 participants