reactivando / validations-br / 17785143100

91%

master: 94%

push

github

fix(release): Correct release-it config and update build tool (#51)

* fix(release): Correct release-it config and update build tool

This commit addresses two issues in the release and build process:

1.  The `release-it` process was failing to publish to npm correctly, likely due to an incomplete package being generated. This has been fixed by making the `release-it` configuration more explicit:
    - Sets `npm.publishPath` to `.` to ensure `release-it` looks for the package in the correct directory.
    - Customizes the `publishCommand` for the `release-it-pnpm` plugin to use a direct `pnpm publish` command, which is better suited for a single-package repository.

2.  A potential build error, reported as `TypeError: Cannot read properties of undefined (reading 'find')`, is addressed by updating `tsdown` to the latest version (`0.15.2`). This should bring in the latest bug fixes for the build tool and its dependencies.

* fix(release): Correct release-it config and update build tool

This commit addresses two issues in the release and build process:

1.  The `release-it` process was failing to publish to npm correctly, likely due to an incomplete package being generated. This has been fixed by making the `release-it` configuration more explicit:
    - Sets `npm.publishPath` to `.` to ensure `release-it` looks for the package in the correct directory.
    - Customizes the `publishCommand` for the `release-it-pnpm` plugin to use a direct `pnpm publish` command, which is better suited for a single-package repository.

2.  A potential build error, reported as `TypeError: Cannot read properties of undefined (reading 'find')`, is addressed by updating `tsdown` to the latest version (`0.15.2`). The `pnpm-lock.yaml` file has been updated accordingly.

* fix(release): Correct release-it config and update build tool

This commit addresses two issues in the release and build process:

1.  The `release-it` process was failing to publish to npm correctly, likely... (continued)

222 of 252 branches covered (88.1%)

Branch coverage included in aggregate %.

693 of 743 relevant lines covered (93.27%)

9.13 hits per line