Skip to content

[BUG] 8.43.3 install fails: @tsed/engines@8.43.3 is missing from npm #3479

Closed

Description

@ueberBrot

Describe the bug

@tsed/platform-views@8.43.3 requires exactly @tsed/engines@8.43.3, but that version of engines is missing from npm. Its latest published version is 8.43.2.

This blocks our upgrade from 8.43.2. npm published platform-views@8.43.3 on October 9, 2026 at 11:28 UTC. The release failed before all packages reached npm.

To Reproduce

In an empty directory, run:

npm init -y
npm install @tsed/platform-views@8.43.3 --package-lock-only --ignore-scripts --no-audit --no-fund --registry=https://registry.npmjs.org

npm exits with code 1 and reports:

npm error code ETARGET
npm error notarget No matching version found for @tsed/engines@8.43.3.

Expected behavior

npm can install @tsed/platform-views@8.43.3 and find all required packages.

Please publish the missing 8.43.3 packages or release a complete newer version.

Code snippets

Repository URL example

No response

OS

macOS (Apple Silicon)

Node version

24.18.1 (npm 12.2.0)

Library version

8.43.3

Additional context

The release log shows that publishing @tsed/engines@8.43.3 failed with:

TLOG_CREATE_ENTRY_ERROR
Invalid response body while trying to fetch https://rekor.sigstore.dev/api/v1/log/entries: aborted

Failed publishing job

A later release attempt also failed:

fatal: tag 'v8.43.3' already exists

Later failed run

The npm registry lists the exact dependency in platform-views, while engines still ends at 8.43.2.

Activity

  1. added theissue type on Oct 12, 2026
  2. github-actions commented on Oct 12, 2026

    @github-actions

    🎉 Are you happy?

    If you appreciated the support, know that it is free and is carried out on personal time ;)

    A support, even a little bit makes a difference for me and continues to bring you answers!

    github opencollective

  3. added a commit that references this issue on Oct 12, 2026
    622b401
  4. Romakita commented on Oct 12, 2026

    @Romakita
    Collaborator

    🎉 This issue has been resolved in version 8.43.4 🎉

    The release is available on:

    Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions