@mercury-fw/plugin-bitbucket 0.1.1 → 0.1.2
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/CHANGELOG.md +11 -0
- package/README.md +1 -1
- package/package.json +7 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,16 @@
|
|
|
1
1
|
# @mercury-fw/plugin-bitbucket
|
|
2
2
|
|
|
3
|
+
## 0.1.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- a493d9b: - A plugin whose CLI keeps its login in a folder declares it in its `package.json` (`mercury.cliCredentials`): `{ folder }` under `~/.config`, the default, or `{ path }` anywhere else under the home. Any plugin's CLI gets the login mechanism, not only the first-party ones.
|
|
8
|
+
- The core unpacks each declared login from its env variable onto the credentials volume (`~/.config`) at startup, only when the folder isn't there yet, for the service and the REPL alike; a folder declared elsewhere in the home lives on the volume under `~/.config/mercury-home`, linked from its usual place. It warns about a declared folder with neither the folder nor the variable.
|
|
9
|
+
- `mfw credentials set|reset <plugin>` names the plugin by its package or its CLI's folder (`@mercury-fw/plugin-jira` or `jira-cli`), read from the app's installed plugins; the short name (`jira`) is no longer accepted, and reset asks for the folder's name.
|
|
10
|
+
- `mfw create` no longer writes `docker-entrypoint.sh` or the credentials variables in the env example, and always mounts the `cli-credentials` volume; an existing app's entrypoint keeps working alongside.
|
|
11
|
+
- The generated README explains how a plugin's CLI gets its login without listing plugins.
|
|
12
|
+
- jira, bitbucket and atlassian-admin declare their CLI's login folder; their READMEs point to `mfw credentials set`.
|
|
13
|
+
|
|
3
14
|
## 0.1.1
|
|
4
15
|
|
|
5
16
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -16,6 +16,6 @@ plugins: [bitbucketPlugin],
|
|
|
16
16
|
|
|
17
17
|
## Credentials
|
|
18
18
|
|
|
19
|
-
The CLI keeps its login under `~/.config/bitbucket-cli`,
|
|
19
|
+
The CLI keeps its login under `~/.config/bitbucket-cli`, and the plugin declares that folder in its `package.json` (`mercury.cliCredentials`). Log in with the CLI's own setup (see [CLI-monorepo](https://github.com/lucabro81/CLI-monorepo)) on your machine, then hand the folder to the app with `mfw credentials set bitbucket-cli`: it travels in the app's env file, and the app unpacks it onto its `cli-credentials` volume at the first start without that folder.
|
|
20
20
|
|
|
21
21
|
MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mercury-fw/plugin-bitbucket",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -24,10 +24,10 @@
|
|
|
24
24
|
"@mercury-fw/utils": ">=0.24.0 <1.0.0"
|
|
25
25
|
},
|
|
26
26
|
"devDependencies": {
|
|
27
|
-
"@mercury-fw/cli-engine": "0.
|
|
28
|
-
"@mercury-fw/plugin-types": "0.
|
|
27
|
+
"@mercury-fw/cli-engine": "0.33.0",
|
|
28
|
+
"@mercury-fw/plugin-types": "0.33.0",
|
|
29
29
|
"@mercury-fw/typescript-config": "*",
|
|
30
|
-
"@mercury-fw/utils": "0.
|
|
30
|
+
"@mercury-fw/utils": "0.33.0",
|
|
31
31
|
"@types/bun": "^1.4.2",
|
|
32
32
|
"typescript": "^6.0.3"
|
|
33
33
|
},
|
|
@@ -48,6 +48,9 @@
|
|
|
48
48
|
"repo": "lucabro81/CLI-monorepo",
|
|
49
49
|
"crate": "bitbucket",
|
|
50
50
|
"version": "0.6.0"
|
|
51
|
+
},
|
|
52
|
+
"cliCredentials": {
|
|
53
|
+
"folder": "bitbucket-cli"
|
|
51
54
|
}
|
|
52
55
|
}
|
|
53
56
|
}
|