semantic-release-pub 0.10.1 → 0.10.3

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.
Files changed (2) hide show
  1. package/README.md +24 -21
  2. package/package.json +15 -15
package/README.md CHANGED
@@ -54,28 +54,9 @@ The plugin can be configured in the [semantic-release configuration file](https:
54
54
 
55
55
  ### `pub.dev` authentication
56
56
 
57
- You can publish to `pub.dev` using either GitHub Actions OIDC or Google Service Account.
57
+ You can publish to `pub.dev` using either Google Service Account or GitHub Actions OIDC.
58
58
 
59
- #### GitHub Actions OIDC
60
-
61
- The following instructions are referenced from the [documentation](https://dart.dev/tools/pub/automated-publishing#configuring-automated-publishing-from-github-actions-on-pub-dev) of Dart. Below are the key steps to allow authentication to `pub.dev` via GitHub Actions OIDC.
62
-
63
- 1. Enable automated publishing.
64
-
65
- > To complete this step, you must have uploader permission on the package or be an admin of the publisher that owns the package.
66
-
67
- 1. Navigate to the package Admin tab (pub.dev/packages/<package>/admin).
68
- 2. Click Enable publishing from GitHub Actions.
69
- 3. Then fill in the necessary information.
70
-
71
- 2. In your workflow, add the `id-token` permission.
72
-
73
- ```yaml
74
- jobs:
75
- publish:
76
- permissions:
77
- id-token: write
78
- ```
59
+ Note that when using GitHub Actions OIDC, `pub.dev` only allows authentication when the workflow is triggered by a `tag` event. See [here](https://github.com/dart-lang/pub-dev/issues/8507) for more details.
79
60
 
80
61
  #### Google Service Account
81
62
 
@@ -109,6 +90,28 @@ The following instructions are referenced from the [documentation](https://dart.
109
90
 
110
91
  5. Copy the content of the JSON key file and set it as an environment variable under `GOOGLE_SERVICE_ACCOUNT_KEY`.
111
92
 
93
+
94
+ #### GitHub Actions OIDC
95
+
96
+ The following instructions are referenced from the [documentation](https://dart.dev/tools/pub/automated-publishing#configuring-automated-publishing-from-github-actions-on-pub-dev) of Dart. Below are the key steps to allow authentication to `pub.dev` via GitHub Actions OIDC.
97
+
98
+ 1. Enable automated publishing.
99
+
100
+ > To complete this step, you must have uploader permission on the package or be an admin of the publisher that owns the package.
101
+
102
+ 1. Navigate to the package Admin tab (pub.dev/packages/<package>/admin).
103
+ 2. Click Enable publishing from GitHub Actions.
104
+ 3. Then fill in the necessary information.
105
+
106
+ 2. In your workflow, add the `id-token` permission.
107
+
108
+ ```yaml
109
+ jobs:
110
+ publish:
111
+ permissions:
112
+ id-token: write
113
+ ```
114
+
112
115
  ### Environment variables
113
116
 
114
117
  | Variable | Description |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "semantic-release-pub",
3
- "version": "0.10.1",
3
+ "version": "0.10.3",
4
4
  "description": "semantic-release plugin to publish a Dart or Flutter package",
5
5
  "main": "dist/index.js",
6
6
  "author": "zeshuaro@gmail.com",
@@ -29,15 +29,15 @@
29
29
  "format": "ESLINT_USE_FLAT_CONFIG=false eslint --ext .ts --fix src tests && prettier --write src/**/*.ts tests/**/*.ts"
30
30
  },
31
31
  "engines": {
32
- "node": ">=22.13.1"
32
+ "node": ">=22.14.0"
33
33
  },
34
34
  "dependencies": {
35
35
  "@actions/core": "^1.11.1",
36
36
  "@semantic-release/error": "^4.0.0",
37
37
  "execa": "^9.5.2",
38
38
  "google-auth-library": "^9.15.1",
39
- "yaml": "^2.7.0",
40
- "zod": "^3.24.1"
39
+ "yaml": "^2.7.1",
40
+ "zod": "^3.24.2"
41
41
  },
42
42
  "devDependencies": {
43
43
  "@semantic-release/changelog": "6.0.3",
@@ -46,22 +46,22 @@
46
46
  "@types/semantic-release": "20.0.6",
47
47
  "@types/semantic-release__error": "3.0.3",
48
48
  "@types/signale": "1.4.7",
49
- "@typescript-eslint/eslint-plugin": "8.21.0",
50
- "@typescript-eslint/parser": "8.21.0",
51
- "@vitest/coverage-v8": "3.0.4",
49
+ "@typescript-eslint/eslint-plugin": "8.29.0",
50
+ "@typescript-eslint/parser": "8.29.0",
51
+ "@vitest/coverage-v8": "3.1.1",
52
52
  "common-tags": "1.8.2",
53
53
  "conventional-changelog-conventionalcommits": "8.0.0",
54
- "eslint": "9.19.0",
55
- "eslint-config-prettier": "^10.0.1",
54
+ "eslint": "9.23.0",
55
+ "eslint-config-prettier": "^10.1.1",
56
56
  "eslint-config-semistandard": "17.0.0",
57
57
  "eslint-config-standard": "17.1.0",
58
58
  "eslint-plugin-import": "2.31.0",
59
- "eslint-plugin-n": "17.15.1",
59
+ "eslint-plugin-n": "17.17.0",
60
60
  "eslint-plugin-promise": "7.2.1",
61
- "prettier": "3.4.2",
62
- "semantic-release": "24.2.1",
63
- "typescript": "5.7.3",
64
- "vitest": "3.0.4",
65
- "vitest-mock-extended": "2.0.2"
61
+ "prettier": "3.5.3",
62
+ "semantic-release": "24.2.3",
63
+ "typescript": "5.8.2",
64
+ "vitest": "3.1.1",
65
+ "vitest-mock-extended": "3.0.1"
66
66
  }
67
67
  }