@quantum-hub/qhubctl 2.2.1 → 2.2.2-next.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -13,6 +13,12 @@ Install it via a [Node version manager](https://github.com/nvm-sh/nvm) or a [Nod
13
13
  npm install -g @quantum-hub/qhubctl
14
14
  ```
15
15
 
16
+ To try the newest prerelease instead, install from the `next` dist-tag:
17
+
18
+ ```bash
19
+ npm install -g @quantum-hub/qhubctl@next
20
+ ```
21
+
16
22
  > **Troubleshooting:** If you see `EACCES permissions` errors, use [nvm](https://github.com/nvm-sh/nvm) or see the [npm docs](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally).
17
23
 
18
24
  ## Usage
@@ -123,6 +129,22 @@ npm run build
123
129
  npm run docs:generate
124
130
  ```
125
131
 
132
+ ## Releasing
133
+
134
+ There are two paths, and the version always comes from the Git tag — the `version` in `package.json` is the placeholder `0.0.0-development` and is never bumped (see [ADR 0003](docs/adr/0003-derive-the-npm-version-from-the-git-tag.md)).
135
+ So `qhubctl --version` from a local build prints the placeholder.
136
+
137
+ **Prereleases** publish automatically, with no review.
138
+ Every `feat`/`fix`/`perf` commit on `main` publishes a `*-next.*` version under the `next` dist-tag.
139
+
140
+ **Final releases** are gated.
141
+ Open a merge request from `main` to the protected `release` branch; merging it publishes the final version under `latest`.
142
+ The merge must fast-forward — a merge commit hides the release tag from `main` and breaks prerelease numbering.
143
+
144
+ > **The prerelease number is a build counter, not a forecast.**
145
+ > Once a prerelease series opens, later commits only increment the counter; the base version never rises.
146
+ > `2.2.2-next.2` can ship as `2.3.0`, leaving a prerelease series on npm with no matching final release.
147
+
126
148
  ## License
127
149
 
128
150
  [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | Copyright 2026-now Kipu Quantum GmbH
@@ -21,14 +21,7 @@ export const setContextCommand = new Command('set-context')
21
21
  .action(async (contextId) => {
22
22
  const userConfig = await requireAuth();
23
23
  const quantumHubService = new QuantumHubService(userConfig);
24
- if (contextId) {
25
- const accounts = await quantumHubService.getAccounts();
26
- const selectedContext = accounts.find(account => account.id === contextId);
27
- if (!selectedContext) {
28
- error(`Context with id "${contextId}" not found.`);
29
- }
30
- }
31
- else {
24
+ if (!contextId) {
32
25
  const spin = spinner('Loading available contexts');
33
26
  const accounts = await quantumHubService.getAccounts();
34
27
  spin.succeed('Contexts loaded');
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quantum-hub/qhubctl",
3
- "version": "2.2.1",
3
+ "version": "2.2.2-next.1",
4
4
  "description": "Kipu Quantum Hub CLI",
5
5
  "author": "Kipu Quantum GmbH",
6
6
  "contributors": [