stdlib-js/math-base-napi-unary is breaking build pipelines

[zac]

Description

The stdlib-js/math-base-napi-unary repo was updated to include git references (in commit d08f2b9) instead of version references (like previously in commit 6fe5d00

This change to point to a git dependency, without an accompanying version update is having unintended effects for working docker containers for instance that were successfully satisfying dependencies without git installed. The official Ghost docker image now can't be built, failing when satisfying dependencies for the Ghost CLI.

Related Issues

docker-library/ghost#460

Questions

No.

Demo

No response

Reproduction

- Check out the docker repo at https://github.com/docker-library/ghost
- Try to build with: `docker build -f 5/bookworm/Dockerfile .`

Expected Results

The docker image is able to pull all dependencies based on the locked versions it uses.

Actual Results

The docker image is not able to pull the dependencies for the locked version, because the locked version changed how dependencies were referenced (and possibly the dependencies code) without a corresponding version change.

Version

No response

Environments

Node.js

Browser Version

No response

Node.js / npm Version

No response

Platform

No response

Checklist

• Read and understood the Code of Conduct.
• Searched for existing issues and pull requests.

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first issue! We will get back to you shortly. 🏃 💨

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

[Planeshifter]

@zac Apologies for the breakage; we are in the middle of a publishing cycle. I have just triggered a new patch release for math-base-napi-unary, version 0.2.5; it now does not depend on git dependencies anymore (a temporary state we ended up with due to the packages not having been published to npm yet). Please let me know if that solves the problem.

[zac]

@Planeshifter Thank you for the quick response! I am not affiliated with Ghost (just having my own Ghost docker images failing and let the official repo know), but I will try to loop in someone on the Ghost CLI project, since it was the CLI's inclusion of the dependency that started showing symptoms. I can update here when I know more.