starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #5415] [feature]: Publish Hoppscotch CLI v2024.6.0 to npm for collection/env ID support #2079

New issue

Closed

opened 2026-03-16 23:05:53 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 23:05:53 +03:00

Owner

Originally created by @ReemaDhiman on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5415

Is there an existing issue for this?

I have searched the existing issues

Summary

Hi Hoppscotch team! 👋

I'm trying to use the latest Hoppscotch CLI features introduced in v2024.6.0, specifically the ability to run tests using collection IDs and environment IDs:

hopp test -e <environment_id> <collection_id> --token <access_token>

However, when I install the CLI via npm (either via npm install -g @hoppscotch/cli or @latest), it still installs v0.25.0, which does not support these features.

Steps to reproduce:

Run: npm install -g @hoppscotch/cli

Run: hopp --ver → outputs 0.25.0

Expected:

CLI version should be v2024.6.0 or newer, with support for ID-based test execution.

Why this matters:

This blocks automation in CI/CD pipelines (e.g., GitHub Actions), as there’s no easy way to access the latest features without building from source.

Ask:

Could you publish the latest CLI version (v2024.6.0 or newer) to npm?

Alternatively, can you provide an official binary release for Linux that we can use in CI environments?

Thank you! 🙏
Happy to help test or provide feedback.

Why should this be worked on?

The latest version of the Hoppscotch CLI (v2024.6.0) introduces critical features such as running collections and environments via their IDs — enabling integration with Hoppscotch Cloud workspaces and improving automation in CI/CD pipelines.

However, since this version is not yet published to npm, users installing @hoppscotch/cli still get v0.25.0, which does not support these features. This creates confusion and blocks adoption of key functionality for those trying to automate tests using collection/env IDs.

Publishing the latest version to npm (or providing official binaries) would make it much easier for teams to:

Integrate Hoppscotch into GitHub Actions, GitLab CI, and other automation platforms

Run API tests via collection/environment IDs instead of exporting JSON manually

Use the latest features as documented in release notes/blogs

This would reduce friction for developers, increase CLI adoption, and help Hoppscotch better support modern testing workflows.

Originally created by @ReemaDhiman on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5415 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Hi Hoppscotch team! 👋 I'm trying to use the latest Hoppscotch CLI features introduced in v2024.6.0, specifically the ability to run tests using collection IDs and environment IDs: hopp test -e <environment_id> <collection_id> --token <access_token> However, when I install the CLI via npm (either via npm install -g @hoppscotch/cli or @latest), it still installs v0.25.0, which does not support these features. Steps to reproduce: Run: npm install -g @hoppscotch/cli Run: hopp --ver → outputs 0.25.0 Expected: CLI version should be v2024.6.0 or newer, with support for ID-based test execution. Why this matters: This blocks automation in CI/CD pipelines (e.g., GitHub Actions), as there’s no easy way to access the latest features without building from source. Ask: Could you publish the latest CLI version (v2024.6.0 or newer) to npm? Alternatively, can you provide an official binary release for Linux that we can use in CI environments? Thank you! 🙏 Happy to help test or provide feedback. ### Why should this be worked on? The latest version of the Hoppscotch CLI (v2024.6.0) introduces critical features such as running collections and environments via their IDs — enabling integration with Hoppscotch Cloud workspaces and improving automation in CI/CD pipelines. However, since this version is not yet published to npm, users installing @hoppscotch/cli still get v0.25.0, which does not support these features. This creates confusion and blocks adoption of key functionality for those trying to automate tests using collection/env IDs. Publishing the latest version to npm (or providing official binaries) would make it much easier for teams to: Integrate Hoppscotch into GitHub Actions, GitLab CI, and other automation platforms Run API tests via collection/environment IDs instead of exporting JSON manually Use the latest features as documented in release notes/blogs This would reduce friction for developers, increase CLI adoption, and help Hoppscotch better support modern testing workflows.

kerem

2026-03-16 23:05:53 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 23:06:09 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Sep 30, 2025):

Hi, Hoppscotch CLI doesn't follow the release cadence of the SH Docker images, hence it follows a different versioning scheme. Hoppscotch Agent is another example.

github.com/hoppscotch/hoppscotch@5039a14985/packages/hoppscotch-agent/package.json (L4)

You can install the latest version of the CLI (v0.25.0 as of today) that supports workspace-based access via supplying collection/environment IDs, etc.

@jamesgeorge007 commented on GitHub (Sep 30, 2025): Hi, Hoppscotch CLI doesn't follow the release cadence of the [SH Docker images](https://hub.docker.com/u/hoppscotch), hence it follows a different versioning scheme. [Hoppscotch Agent](https://docs.hoppscotch.io/documentation/features/interceptor#hoppscotch-agent) is another example. https://github.com/hoppscotch/hoppscotch/blob/5039a149859ad42e8d0435d13b90531a2a202c3a/packages/hoppscotch-agent/package.json#L4 You can install the latest version of the [CLI](https://www.npmjs.com/package/@hoppscotch/cli) (`v0.25.0` as of today) that supports [workspace-based](https://docs.hoppscotch.io/documentation/clients/cli/overview#running-collections-present-on-the-api-client) access via supplying collection/environment IDs, etc.

kerem commented

2026-03-16 23:06:14 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Oct 1, 2025):

Closing, feel free to let us know if you have further questions.

@jamesgeorge007 commented on GitHub (Oct 1, 2025): Closing, feel free to let us know if you have further questions.

kerem referenced this issue

2026-03-17 01:13:34 +03:00

[PR #2104] [MERGED] feat: handle test script execution failure #3628